API overview
Server-side REST API for sending events, identifying users, and receiving real-time decisions via webhooks. Pair with the SDKs for client-side capture, or use standalone for backend integrations.
Base URL
⚠ TODO — Engineering
Document the base URL(s) for the Appice REST API. List per-region endpoints if the deployment is regional (IN / SEA / MENA / LatAm). Include both the production and any staging URLs.
Format
All requests and responses use application/json. All timestamps are ISO 8601 in UTC unless otherwise noted.
Authentication
All endpoints require authentication. See Authentication for details.
Rate limits
⚠ TODO — Engineering
Document the per-token / per-endpoint rate limits. Include the response headers (
X-RateLimit-*) and what happens on exceed (HTTP 429 — link to Errors).Versioning
⚠ TODO — Engineering
Document the versioning policy. Include where the version is communicated (URL path, header, or implicit), what counts as a breaking change, and the deprecation notice window.
Sandbox
⚠ TODO — Engineering
If a sandbox/test environment is offered, document how to access it, how it differs from production, and any sandbox-only limitations.