Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt

Use this file to discover all available pages before exploring further.

This is the first change to how you access SQD data since we opened up public datasets in 2023. If you’re on SQD Cloud, this won’t affect you. If you are self-hosting a squid or are otherwise calling gateway endpoints from outside of SQD Cloud, read on.
Starting Monday, May 19 at 12:00 UTC (two weeks from today), external calls to gateway endpoints will need an API key. Same endpoints, same data, same response shapes, just authenticated. Unauthenticated requests will return HTTP 401 from that point.
Keys are live now. You can generate one and start using it today, ahead of the May 19 cutoff.

​
What to do

On SQD Cloud

Nothing on your side. Squids running in Cloud keep working through the cutoff and after.

Accessing SQD data with API keys

If you’re hitting gateway endpoints from outside Cloud, generate an API key and attach it to your requests.

​
What’s next

Portal is where we’re investing going forward. Later this year, gateways will be sunset. We’ll share the date as soon as we have it. Before that, some datasets will be deprecated entirely. API keys are coming to Portal in the next phase too, alongside pricing tiers.

​
FAQ

No. Cloud squids keep working as-is. The change only affects requests to gateway endpoints from outside Cloud.
Requests without a key will return HTTP 401 from 12:00 UTC on May 19 onwards.
Yes. Keys are live now. Generate one, attach it to your requests, and you’re set ahead of the cutoff.
Not yet. Portal API keys are coming in the next phase, alongside pricing tiers. We’ll give the same kind of notice before that lands.
Later this year. We’ll announce a specific date separately. Some datasets will be deprecated entirely before then.
No. If your processor doesn’t have a .setGateway() call, this change doesn’t apply.
Going forward, we’ll post announcements here in the changelog and in our Telegram community. Those are our primary channels. Questions? Get in touch.