Delete a leaderboard
DELETE
/leaderboards/{leaderboardID}
Authorization headerleaderboardcommunityID401 if missing, invalid, or insufficientdelete:leaderboard command through the partner publisher pathleaderboardID must identify a leaderboard in the API-key's community404 when the leaderboard does not exist or is not in the resolved communityPATCH /leaderboards/{leaderboardID} if the leaderboard should remain availableDELETE /leaderboards/507f1f77bcf86cd799439012How to use it: Send a DELETE request to
/leaderboards/{leaderboardID} with the request body, query parameters, or multipart fields shown below. Partner API key required when this surface is enabled for the community. Confirm gateway access before using in production.Availability note: this route is legacy or partner-service-backed. During a 2026-05-18 smoke test, the equivalent root path returned 404 on
https://api.returning.ai; keep it marked non-primary until the gateway alias is confirmed.Successful response: HTTP 200. The body follows the endpoint schema; many integration endpoints wrap the useful payload under
data with status and message.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 target resource, route, or community-scoped record was not found.409 duplicate or conflicting state for create/update operations, where applicable.500 unexpected Returning.AI service error.Request
Path Params
Header Params
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request DELETE 'https://api.returning.ai/leaderboards/507f1f77bcf86cd799439012' \
--header 'Authorization: Bearer XXXXXX'Response Response Example
200 - Success Example
{
"meta": {
"status": "success",
"statusCode": 200
},
"message": "Delete leaderboard success.",
"data": "507f1f77bcf86cd799439012"
}Modified at 2026-05-18 17:03:37