Secure an Adjust S2S events integration against spoofed requests using S2S Security tokens

domain: dev.adjust.com/en/api/s2s-api · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Generate a new S2S Security token in the Adjust dashboard under the app's Protection tab, S2S Security section
  2. Choose the appropriate token scope(s) — Events, Sessions, or Ad revenue — matching which S2S endpoints the token should authorize
  3. Add the token as an Authorization: Bearer header on every S2S request (e.g. the /event endpoint call)
  4. Test the token thoroughly in requests before activating S2S authentication enforcement in the dashboard
  5. Handle rejected requests: a 202 response indicates a missing or wrong token, and a 401 indicates the token's scope doesn't cover the requested action

Known gotchas

Related routes

implement adjust server-to-server (s2s) event callbacks with security tokens
dev.adjust.com · 5 steps · unrated
Send in-app events to Adjust via the Server-to-Server (S2S) Events API
dev.adjust.com · 5 steps · unrated
Send a custom in-app event from your server to Adjust via the S2S events API
dev.adjust.com/en/api/s2s-api · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans