#1

I’ve been using the 30day subscription and now have the queries working well, but am realizing I need data further back than 30 days.

So I’m considering switching to the Full Archive, as the fewer allowed calls per month won’t be an issue for me.

However, I’m curious if there are any other differences in the query or the data, or will all my current queries work by just changing the endpoint?

I.e., here’s a 30day query I’ve been using.

twurl "/1.1/tweets/search/30day/a9k.json" -A "Content-Type: application/json" -d '{"query":"@CaptMarvelNews OR \"captain marvel\" lang:en", "maxResults":"100", "fromDate":"201904010001", "toDate":"201904112359"}'

Will that be the same for the Full Archive, with the exception of changing the endpoint link from /30day/ to /fullarchive/, like below?

twurl "/1.1/tweets/search/fullarchive/a9k.json" -A "Content-Type: application/json" -d '{"query":"@CaptMarvelNews OR \"captain marvel\" lang:en", "maxResults":"100", "fromDate":"201904010001", "toDate":"201904112359"}'

Thx
doug

#2

Yes, fullarchive is going to work exactly the same (provided you have the dev environment set up, it’s separate to 30day).

I’d pay attention to the fromDate and toDate parameters - to make sure that calls to fullarchive are genuinely beyond 30 days, so you’re not wasting calls. Also, if you don’t specify those the default for fullarchive is to return results from the last 30 days, like 30day endpoint.

Another thing to keep in mind is, the further back you go, the more you’ll encounter features that don’t work because of changes over time on the platform - those are good to keep in mind Full-archive search - Metadata and filtering timeline | Docs | Twitter Developer Platform

1 Like
#3

Thanks, Igor. Great input. The timeline line is excellent info.

#4