Authentication

Every request must include your API key in the Authorization header:

Authorization: Bearer <your-api-key>

Keys are issued with the sf_api_ prefix. Requests without a valid Bearer token receive 401; a valid key that lacks access to the requested resource receives 403 — both use the same error envelope.

Example

curl -sS -X POST "https://api.snitchfeed.com/v1/data/twitter/tweets/search" \
  -H "Authorization: Bearer sf_api_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"query":"example"}'

Creating an API key

1. Open Integrations → API in your SnitchFeed workspace (app).
2. Create a key and copy it immediately — the full secret is only shown once.

Access to the HTTP API requires a plan that includes API access. If your organization is not eligible, key creation and requests will be rejected.

Building an integration that other customers will install? Use OAuth instead of asking customers for their API key.

Security

• Store keys in environment variables or a secrets manager, not in source control.
• Rotate keys from the same page if they are exposed or no longer needed.
• Keys are scoped to a single workspace, not shared across workspaces.