API documentation
RFC 9457 problem types

Developer API error reference

Every REST and MCP transport error includes a stable code, a dereferenceable type URL, and a request ID. Use the request ID when contacting support.

api_disabled
HTTP 503

API temporarily unavailable

The requested Comidoc developer surface is disabled.

Resolution: Retry later or check the developer documentation for service updates.

Too many authentication failures

Too many failed authentication attempts came from this address.

Resolution: Wait for the rate-limit window to reset before trying again.

API temporarily unavailable

The API request context could not be initialized.

Resolution: Retry shortly. Contact Comidoc if the problem persists.

Course not found

No active course matches the supplied Udemy course ID or slug.

Resolution: Check the identifier or search the course catalog first.

Developer account unavailable

The developer account associated with this request is not active.

Resolution: Open the developer portal or contact Comidoc support.

Insufficient API key scope

The API key does not grant the scope required by this endpoint.

Resolution: Create or rotate a key with the required read scope.

Internal API error

The API could not complete the request because of an internal error.

Resolution: Retry with backoff and provide the request ID if the problem persists.

Invalid API key

The supplied API key is invalid, expired, or revoked.

Resolution: Create or rotate a key in the developer portal.

Invalid Content-Length

The MCP request contains an invalid Content-Length header.

Resolution: Send a valid non-negative Content-Length value or let the HTTP client set it.

Invalid filter value

A category, language, or level does not belong to the current canonical vocabulary.

Resolution: Use GET /api/v1/filter-options or the MCP get_filter_options tool.

Invalid query parameters

One or more query parameters do not satisfy the endpoint contract.

Resolution: Correct the reported fields and retry the request.

Invalid RapidAPI request

The RapidAPI proxy identity could not be verified.

Resolution: Send requests through the configured RapidAPI proxy.

Invalid MCP request body

The MCP HTTP request body could not be read or decoded.

Resolution: Send a valid MCP JSON-RPC request body.

MCP request failed

The MCP server could not complete the protocol request.

Resolution: Retry with backoff and provide the request ID if the problem persists.

Anonymous MCP quota exceeded

The anonymous MCP hourly quota has been exhausted.

Resolution: Wait for the reset or authenticate with a Comidoc API key from https://comidoc.com/developers.

MCP transport rate limit exceeded

Too many MCP protocol requests came from this address.

Resolution: Reduce protocol polling and wait for the transport window to reset.

API key required

This endpoint requires a Comidoc developer API key.

Resolution: Send Authorization: Bearer cmd_live_… with a key from https://comidoc.com/developers.

API quota exceeded

The developer account monthly quota has been exhausted.

Resolution: Review usage and plan options at https://comidoc.com/developers.

MCP request body too large

The MCP request body exceeds the accepted transport limit.

Resolution: Reduce the request size and retry.

Quota service unavailable

Comidoc could not read or update the request quota safely.

Resolution: Retry shortly. The API fails closed while quota state is unavailable.

API quota exceeded

Too many API requests were sent in a short period.

Resolution: Retry after the reported delay and reduce request concurrency.

Topic not found

No Comidoc topic matches the supplied slug.

Resolution: Use GET /api/v1/topics or the MCP list_topics tool to discover valid slugs.

Unsupported media type

The MCP endpoint received an unsupported request content type.

Resolution: Send MCP JSON-RPC requests with Content-Type: application/json.