Authentication

You'll need to authenticate your requests to access any of the endpoints in the Adlocaite API. Authentication is handled exclusively through Bearer tokens provided by our onboarding team during the integration process.

Bearer token authentication

The Adlocaite API uses Bearer token authentication for all requests. Your API key will be provided by our onboarding team along with your integration documentation. Here's how to authenticate using cURL:

curl https://api.adlocaite.com/functions/v1/api/offers/request/[screenId]?min_bid_cents=200 \
  -H "Authorization: Bearer YOUR_API_KEY"

Getting your API key

API keys are distributed exclusively through our onboarding process to ensure quality and security:

1. Contact our onboarding team to begin the integration process
2. Complete the technical evaluation to ensure compatibility
3. Receive your API key along with detailed integration documentation
4. Test on the staging environment (staging.api.adlocaite.com) or with demo offers (?demo=true) before going live

Security best practices

• Keep your API key secure and never expose it in client-side code
• Use HTTPS for all API requests
• Store your key safely using environment variables or secure key management
• Contact us immediately if you suspect your key has been compromised

# Store in environment variable
export ADLOCAITE_API_KEY="your_api_key_here"

# Use in requests
curl https://api.adlocaite.com/functions/v1/api/offers/request/[screenId]?min_bid_cents=200 \
  -H "Authorization: Bearer $ADLOCAITE_API_KEY"

API key permissions

Your API key provides access to:

• Offer retrieval for your assigned screens
• Offer responses (accept/decline)
• Asset caching information for optimization

Rate limiting

There are currently no fixed, published rate limits per API key. We ask integrations to poll responsibly: request offers when a playout slot actually needs to be filled, and avoid tight retry loops.

If the platform is under heavy load you may receive an HTTP 429 Too Many Requests response. In that case, retry with exponential backoff. If your use case requires sustained high request volumes (for example a large screen network), talk to our onboarding team so we can plan for it.