What this endpoint does#
This page documents the user API key surface (/v1/users/apikeys, /v1/api-key-info, and the user-scoped update/delete paths). Those routes are not mounted on https://api.returning.ai.Do not generate user-key scripts from these pages. Manage community API keys instead.GET/POST /v1/communities/{communityId}/api-keys and PUT/DELETE /v1/communities/{communityId}/api-keys/{apiKeyId}.
Quick start#
Do not call the user-key routes for integrations:404 Route not found error. detail: Cannot GET /apis/v1/users/apikeys.Authentication and permission#
A valid community key does not mount these paths. Adding user-key permissions will not change that.Intended user-key permission names (sendMessages, replyMessages, reactToMessages) are not interchangeable with community names (sendMessage, replyMessage).Complete examples#
There is no success example on this gateway.Update/delete pages in Apidog currently hard-code path ObjectIds. Do not copy those ids.Success and readback#
No success response. For community keys, list by community ObjectId and match name. Create returns key once. List also returns key.Errors and recovery#
| Status | When | Recovery |
|---|
404 Cannot GET /apis/v1/users/apikeys | User key list | Use community API key routes. |
404 | /v1/api-key-info | List community keys by name. |
Retry safety#
Repeating these GETs will not mount the routes.
Gotchas#
Widget WIDGET_API_KEY is a different credential than these user API key routes.
Next steps#
Read community API keys
List community keys. Treat data[].key as secret-bearing.