List servers

Legacy category: This endpoint is retained for compatibility, historical admin tooling, or test workflows. Do not use it as the default choice for new integrations unless the backend team confirms this exact route is still supported for your community.

What it is for: List servers.

How to use it: Send a GET request to /servers with the documented body, query parameters, headers, or multipart fields. Prefer the newer authenticated /v1/... integration API where available.

Successful response: HTTP 2xx. Older endpoints may return a legacy response envelope or a resource-specific payload rather than the newer { status, message, data } wrapper.

Common error states:

400 invalid request body, query, ObjectId, pagination, file format, or missing required field.

401 missing, invalid, expired, or insufficient API key/token.

403 key is valid but cannot access this community/channel/user/resource, where supported by the service.

404 route or target resource was not found. Several legacy root routes returned 404 on https://api.returning.ai during smoke testing and need backend confirmation before external use.

409 duplicate or conflicting state for create/update operations, where applicable.

500 unexpected Returning.AI service error.

Legacy status:
Compatibility endpoint retained for older integrations. Do not use this endpoint for new integrations unless Returning.AI specifically tells you to maintain a legacy flow. Prefer the current /v1/... endpoint in the matching non-Legacy category when one exists.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

{ "meta": { "success": true, "message": "My servers", "devMessage": "My servers" }, "body": [ { "_id": "{_id}", "name": "Dummy Server", "image": "https://dummyimage.com/600x400/000/fff", "owner": { "id": "2" }, "__v": 0, "roles": [], "categories": [], "leaderboards": [], "languageSettings": [], "id": "{_id}" } ] }

Request

Responses