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.
Reseller accounts only. Request access.
ID of the client user who owns the key.
The key's ID, or 0 for the default key the account got at signup.
curl -X POST 'https://backend.omnidim.io/api/v1/reseller/users/api-keys/revoke' \ -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{ "user_id": 1234, "api_key_id": 88 }'
{ "success": true, "revoked": true, "api_key_id": 88 }
BearerAuthAuthorizationBearer <token>Bearer token authentication. Obtain your API key from the OmniDimension dashboard.
application/jsonuser_id*integerID of the client user who owns the key.
api_key_id*integerThe key's ID, or 0 for the default key the account got at signup.
0 <= valueResponse body
application/jsonKey revoked.
application/jsonsuccess?booleanrevoked?booleanapi_key_id?integerIssue 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.
Set child concurrency limit
Set the maximum number of simultaneous calls a client can run. new_limit is the absolute figure you want, not a change to the current one.
