Base URL
Authentication
All API requests require authentication via API key:Request Format
Headers
| Header | Required | Description |
|---|---|---|
X-API-Key | Yes | Your project API key |
Content-Type | Yes* | application/json for POST/PUT/PATCH |
X-Idempotency-Key | No | Unique key for idempotent requests |
Request Body
All request bodies should be JSON:Response Format
Success Response
Error Response
HTTP Status Codes
| Status | Description |
|---|---|
200 OK | Request succeeded |
201 Created | Resource created successfully |
400 Bad Request | Invalid request parameters |
401 Unauthorized | Missing or invalid authentication |
403 Forbidden | Insufficient permissions |
404 Not Found | Resource not found |
409 Conflict | Resource already exists |
429 Too Many Requests | Rate limit exceeded |
500 Internal Server Error | Server error |
Pagination
List endpoints support pagination:Filtering & Sorting
Many endpoints support filtering and sorting:Idempotency
For POST requests, use theX-Idempotency-Key header to ensure idempotent operations:
Idempotency keys are valid for 24 hours. Requests with the same key within
this window will return the same response.
API Endpoints
Players
Manage player profiles, XP, levels, and currencies
Events
Track player actions and trigger gamification rules
Quests
Create and manage quest progress
Adventures
Seasonal content and quest collections
Leaderboards
Real-time rankings and competitions
Lobbies
Multiplayer lobby management
Chat
Real-time messaging
Rules
Configure gamification logic
SDKs
We provide official SDKs for easier integration:| Language | Package | Documentation |
|---|---|---|
| JavaScript/TypeScript | @engagefabric/sdk | SDK Docs |
| React | @engagefabric/react | React Docs |
OpenAPI Specification
Download the complete OpenAPI specification:OpenAPI Spec
Download the OpenAPI 3.0 specification for code generation and API exploration