API integration
If your business already has its own software (a school management system, a gym CRM, etc.), API integration lets that software talk to SUQO. This page covers what most non-developer sellers need: creating and managing API keys.
You can hold several keys at once, each with its own name and expiry — so you can give one key per integration and revoke just that one if it's ever exposed.
Before you start
API keys require verified KYC. Until your KYC is approved the page prompts you to complete it and no keys can be created — see KYC verification.
Creating a key
- Open Configuration → API integration.
- Click Create API key.
- Give the key a name — something that says where it's used, like "Gym CRM" or "Website booking form". This is how you'll tell your keys apart later.
- Choose an expiry: 1 day, 7 days, 30 days, Custom, or Never.
- Custom takes a number plus a unit — up to 365 days or 12 months.
- Never means the key stays valid until you delete it.
- Click Create.
SUQO shows the full key once, on screen, right after it's created. Copy it then and store it in your software's secret-management system.
The keys table
| Column | Description |
|---|---|
| Name | The name you gave the key. |
| Key | A masked version — enough to recognise which key a row is, not enough to use. |
| Created | The date the key was created. |
| Expires | The expiry date, or a dash for keys set to never expire. |
| Last used | When the key last made a request — shown as "Just now", "N minutes ago", "N hours ago" for recent activity, otherwise a date. Never means the key has not been used yet. |
| Status | Active, or Inactive once the key is past its expiry. |
Last used is the quickest way to spot a key you can safely delete: a key that has never been used, or hasn't been used in months, is probably an integration that no longer exists.
Deleting a key
Click the delete icon on the key's row and confirm. The key stops working immediately, and any software still using it starts getting authentication errors — so update that software first if it's still in use.
Deleting one key never affects the others.
Expired keys
An expired key stays in the list with Inactive status instead of disappearing, so you can see what expired and when. It can't authenticate any more. Create a replacement and delete the expired row once your software is updated.
What your developer needs
Hand your developer a key and a link to the SUQO API reference. They'll want Authentication first, and the Sandbox guide for testing without touching live data.