This key authorizes your backend to send rewards securely without exposing credentials to the client.
Store this key securely, it will not be displayed again after creation. Save it immediately in your environment variables or secrets manager.
Configuration
Header Parameters
Client identifier (use
“developer-dashboard” )Bearer token for authenticationFormat:
Bearer {JWT_TOKEN}Path Parameters
Your Rewards App ID.
Response Fields
| Field | Type | Description |
|---|---|---|
success | boolean | Whether the request was successful |
message | string | Description of the result |
data | object | Contains API key details |
id | string | Unique identifier for this API key |
apiKey | string | The actual API key to use for server authentication. Store securely! |
createdAt | string | ISO 8601 timestamp of when the key was created |
Response Status Codes
| Code | Description |
|---|---|
201 | API key created successfully |
400 | Bad request - invalid UUID |
401 | Unauthorized - authentication required |
403 | Forbidden - developer does not own this app |
409 | Conflict - race condition detected |
500 | Internal server error |
This API key will only be shown once in the response. If you lose it, you’ll need to create a new key and revoke the old one.
Code Examples
Try It Out
Ready to create your first API key? Use our API playground on the right to test with your JWT token.What’s Next?
Now that you’ve created an API key, your backend can authenticate securely with the ZBD Rewards API.In the next step, you’ll learn how to send rewards directly from your server using the v2 API endpoint.