IZI API: Developer Overview
IZI API: Developer Overview
Section titled “IZI API: Developer Overview”IZI API is a GraphQL interface for integrating external systems with the gaming club management platform. Partners use it to connect POS systems, payment gateways, mobile apps, and custom dashboards.
One endpoint, one protocol — no multiple REST resources to track.
Architecture
Section titled “Architecture”Client (partner) │ │ POST https://api.izi.is/graphql │ Authorization: Bearer <jwt_token> ▼ GraphQL Gateway │ ├── Clubs & Zones ├── Sessions & Devices ├── Clients & Balances ├── Tariffs & Payments ├── Analytics └── WebhooksAll operations go through a single endpoint. Queries (query) read data, mutations (mutation) change state, subscriptions (subscription) stream real-time events.
Basic Request
Section titled “Basic Request”curl -X POST https://api.izi.is/graphql \ -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_TOKEN" \ -d '{"query": "{ me { id email } }"}'Response format is always { "data": {...}, "errors": [...] }. If errors is present, the request was partially executed or rejected.
Available API Domains
Section titled “Available API Domains”| Domain | Example Operations |
|---|---|
| Auth | loginWithEmailPassword, refreshToken |
| Clubs | clubs, club, createClub, updateClub |
| Devices | devices, deviceStatus, updateDevice |
| Sessions | activeSessions, startSession, endSession |
| Clients | clients, clientByPhone, topUpBalance |
| Tariffs | tariffs, purchaseTariff |
| Analytics | analyticsRevenue, analyticsOccupancy |
| Webhooks | createWebhook, webhooks, deleteWebhook |
Versioning
Section titled “Versioning”IZI API does not use URL versioning (/v1/, /v2/). Changes are made via deprecation: old fields are marked @deprecated with replacement info, new fields are added in parallel. IZI notifies partners 30 days before field removal.
Check field status:
{ __type(name: "Session") { fields { name isDeprecated deprecationReason } }}Limits and Availability
Section titled “Limits and Availability”- Rate limit: 100 requests / 10 seconds per token — see Rate Limits
- Availability: 99.9% SLA for production cluster
- Region: EU (Frankfurt) primary, UAE secondary
Next Steps
Section titled “Next Steps”- GraphQL Basics in IZI — how to build queries
- Authentication & Tokens — getting and refreshing JWT
- Webhooks — subscribing to real-time events
- SDK Examples — ready-to-use JS and Python code
Frequently asked questions
What protocol does IZI API use?
IZI API is GraphQL-based. All requests are POST to a single endpoint: https://api.izi.is/graphql
Does IZI API use OAuth?
No. IZI uses JWT tokens. Get a token via the loginWithEmailPassword mutation and pass it in Authorization: Bearer <token> header.
Is there a REST API?
No public REST API. All interaction goes through the GraphQL endpoint.
How do I get sandbox access?
Sandbox access is available on request through the IZI team. Contact your integration manager.