Issue a client API key
Issue a named API key for a user in one of your client organizations. The secret is in this response only, so store it now. No listing shows it again. To rotate a key, issue a new one, switch the integration to it, then revoke the old one.
Reseller accounts only. Request access.
ID of the client user who will own the key.
A name for the key. Must be unique among that user's keys.
curl -X POST 'https://backend.omnidim.io/api/v1/reseller/users/api-keys' \ -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{ "user_id": 1234, "name": "n8n" }'
{ "success": true, "user_id": 1234, "api_key_id": 88, "name": "n8n", "api_key": "YOUR_NEW_KEY" }
BearerAuthAuthorizationBearer <token>Bearer token authentication. Obtain your API key from the OmniDimension dashboard.
application/jsonuser_id*integerID of the client user who will own the key.
name*stringA name for the key. Must be unique among that user's keys.
Response body
application/jsonKey issued.
application/jsonsuccess?booleanuser_id?integerapi_key_id?integername?stringapi_key?stringThe secret. Shown only in this response.
Update user expiry
Set or remove the expiry date on a child user. The user must belong to a child organization of your reseller.
Revoke a client API key
Revoke one of a client user's API keys. The key stops working on the next request. Pass the key's api_key_id, or 0 for the default key every account gets at signup. Revoking a key that is already revoked succeeds. GET /reseller/organizations lists each user's active keys by id and name.
