Skip to Content
CallMitraDocs
Errors

resource_not_found

The requested resource was not found.

HTTP statusTypeCode
404not_found_errorresource_not_found

What it means

The URL or the id in it does not match anything your workspace can see. Check the id and the endpoint path.

How to handle it

Check the ID in the path. It may be wrong, deleted, or belong to another workspace; the API answers 404 rather than revealing other workspaces’ data.

Example response

{
  "detail": "The requested resource was not found.",
  "error": {
    "type": "not_found_error",
    "code": "resource_not_found",
    "message": "The requested resource was not found.",
    "param": null,
    "docUrl": "https://docs.callmitra.ai/errors/resource_not_found",
    "requestId": "req_3f9c2a7d1b8e4c6a9f0e2d4b6a8c0e1f"
  }
}

Branch on error.code; it never changes once published. The message text can change. See Errors for the envelope.

Returned by

  • POST /api/v1/tickets/{ticket_id}/activities — Add a note to a ticket
  • POST /api/v1/agents/ — Create an agent
  • POST /api/v1/campaigns/ — Create an empty campaign
  • POST /api/v1/campaigns/create-with-leads — Create a campaign with its leads
  • POST /api/v1/tickets/ — Create a ticket
  • GET /api/v1/tickets/{ticket_id} — Get a ticket
  • GET /api/v1/whatsapp/messages/{message_id} — Get a WhatsApp message
  • GET /api/v1/tickets/{ticket_id}/activities — List ticket activities
  • GET /api/v1/whatsapp/message-templates — List WhatsApp templates
  • POST /api/v1/tickets/{ticket_id}/replies — Reply to the customer
  • POST /api/v1/whatsapp/messages — Send a WhatsApp message
  • PUT /api/v1/campaigns/{campaign_id} — Update a campaign
  • PATCH /api/v1/tickets/{ticket_id} — Update a ticket

On this page