Why Am I Getting "Account/Subscription/Transaction/Invoice not found" (HTTP 404) when I use the Recurly API? – Recurly

When using the Recurly API, you may encounter a 404 Not Found error that includes messages such as: "Account not found", "Subscription not found", "Transaction not found", or "Invoice not found". These errors mean that Recurly could not locate the object referenced by your request. Most of the time, this is caused by issues with the API key, identifier format, or a typo in the request.

Last updated: 2025-09-04

Common Reasons for "Not Found" Errors

1. Wrong API Key

Check that you’re using a valid API key belonging to the correct site (Sandbox vs. Production).
Make sure the key has the required permissions for the request.

2. Missing Prefix (uuid- or code-)

Some Recurly endpoints require you to explicitly prefix the resource identifier.
For example, use uuid-123456 or code-myaccount when specifying a UUID or a code instead of an ID.
Requests without the correct prefix will return 404 Not Found.

3. Misspelled Identifier

Identifiers are case-sensitive and must match exactly.
Double-check for typos when entering account_code, subscription_id, transaction_id, or invoice_id.

Troubleshooting Steps

Verify the API key being used is valid, active, and belongs to the correct site.
Check whether the identifier requires a uuid- or code- prefix.
Confirm there are no typos in the identifier string.

Fail Safe

Always log both the request and response to help identify root causes.
If you are unsure whether a resource exists, confirm in the Recurly Admin UI.
Contact Recurly Support if the errors persist, providing example requests and timestamps.

Resources