Developer reference
ADJODO API
JSON REST endpoints are served below /api. Private endpoints require Authorization: Token YOUR_TOKEN. Never expose tokens in client URLs or logs.
curl https://api.example.com/api/auth/me/ \
-H "Authorization: Token YOUR_TOKEN"Authentication
POST
/api/auth/signup/Create advertiser or publisher accountPOST
/api/auth/login/Receive an API tokenGET/PATCH
/api/auth/me/Read or update your own profileCampaigns
GET/POST
/api/campaigns/List owned/eligible campaigns or create onePOST
/api/campaigns/validate-url/Validate a public campaign URLGET
/api/campaigns/{id}/performance/Owner-scoped campaign performanceTracking
GET/POST
/api/tracking/links/Publisher-owned tracking linksGET
/api/tracking/go/{code}/Public click redirectPOST
/api/tracking/postback/Token-authenticated conversion postbackWallet
GET
/api/wallet/Current user's walletGET
/api/wallet/transactions/Own transaction ledgerPOST
/api/wallet/withdrawals/Create an eligible withdrawalAPI keys & webhooks
GET/POST
/api/integrations/keys/List or create server API keysDELETE
/api/integrations/keys/{id}/Revoke an API keyGET
/api/integrations/v1/me/API-key authenticated identityGET
/api/integrations/v1/campaigns/Role-scoped campaign list using X-API-KeyGET/POST
/api/integrations/webhooks/Manage HMAC-signed HTTPS endpointsPOST
/api/integrations/webhooks/{id}/test/Send a test webhookIntegration notes
Webhooks require provider signatures or campaign tokens. Conversion identifiers must remain stable across retries. Requests are throttled and object ownership is enforced server-side.