Copy page

Error codes

resource_not_found

Resource not found. The id does not name a resource this key can see. Ids are scoped to a workspace and a mode: a live-mode id is not found with a test key and vice versa, and another workspace's id is not found either.

What it means

The API returns HTTP 404 with error.code set to resource_not_found. The default message is: "No such resource."

Common causes

• A typo or a truncated id.
• An id from the other mode (test vs live).
• An id with the wrong prefix for this resource.
• The resource was deleted.

How to identify it

Check the response status (404) and error.code (resource_not_found). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.

How to fix it

• Check the id and the key mode. List the resource to find valid ids.

Retry guidance

Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.

Did anything happen?

This request was refused before any call was placed and before anything was charged.

Idempotency

Nothing was done and nothing was stored (under an Idempotency-Key, if you sent one), so the request can be sent again, with the same key if you used one, once the cause is fixed.

Who can fix it

The developer who sends the request can fix it; no administrator action is normally needed.

When to contact support

If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).

Example error response

JSON
{
  "error": {
    "code": "resource_not_found",
    "message": "No such resource.",
    "details": {},
    "request_id": "req_bic5uwhfw3xxme7xdhmjberw",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/resource_not_found"
  }
}

Operations that can return this error

• GET /agents/{agent_id}: Retrieve an agent
• GET /agents/{agent_id}/readiness: Check whether an agent can place calls
• GET /phone-numbers/{phone_number_id}: Retrieve a phone number
• GET /calls/{call_id}: Retrieve a call
• GET /calls/{call_id}/transcript: Retrieve a call transcript
• GET /calls/{call_id}/recording: Retrieve a call recording link
• GET /calls/{call_id}/analysis: Retrieve a call analysis
• GET /recordings/{recording_token}: Download recording audio
• GET /campaigns/{campaign_id}: Retrieve a campaign
• PATCH /campaigns/{campaign_id}: Update a campaign
• POST /campaigns/{campaign_id}/recipients: Add recipients
• GET /campaigns/{campaign_id}/recipients: List recipients
• POST /campaigns/{campaign_id}/start: Start a campaign
• POST /campaigns/{campaign_id}/pause: Pause a campaign
• POST /campaigns/{campaign_id}/resume: Resume a campaign
• POST /campaigns/{campaign_id}/stop: Stop a campaign
• GET /contacts/{contact_id}: Retrieve a contact
• PATCH /contacts/{contact_id}: Update a contact
• DELETE /contacts/{contact_id}: Delete a contact
• DELETE /dnc-entries/{dnc_entry_id}: Remove a number from the do-not-call list
• GET /webhook-endpoints/{webhook_endpoint_id}: Retrieve a webhook endpoint
• PATCH /webhook-endpoints/{webhook_endpoint_id}: Update a webhook endpoint
• DELETE /webhook-endpoints/{webhook_endpoint_id}: Delete a webhook endpoint
• POST /webhook-endpoints/{webhook_endpoint_id}/rotate-secret: Rotate a webhook signing secret
• POST /webhook-endpoints/{webhook_endpoint_id}/test: Send a test event
• GET /webhook-endpoints/{webhook_endpoint_id}/deliveries: List deliveries
• POST /webhook-deliveries/{webhook_delivery_id}/retry: Retry a delivery
• POST /calls: Place a call
• POST /campaigns: Create a campaign
• PATCH /campaigns/{campaign_id}: Update a campaign

See all codes in the error-code reference.