The RESOURCE_NOT_FOUND error occurs when the system fails to locate a requested resource using the supplied identifier or ID. This error typically arises during operations such as retrieving, updating, authorizing, or processing orders.
Common Causes:
-
Incorrect or Invalid Resource ID: This error occurs when the resource ID provided in the API request is either incorrect or invalid. This means that the system cannot find the specific resource you're trying to access because the given identifier doesn't match any of the existing resources. It could be due to a typo or a mismatched ID.
-
Non-Existent Resource Identifiers: This error code may also indicate that the resource identifier or token ID you are trying to access is expired because PayPal will not store it once it expired. By default, a resource ID expires after 3 hours.
-
Issues with API Endpoint Access: This error occurs when you are accessing the incorrect API endpoint, such as checking a Live environment resource ID with a Sandbox endpoint. Such issues may result in setting up incorrect configurations on your system, which prevents you from accessing the desired resource.
Example of API Error Response:
{
"name": "RESOURCE_NOT_FOUND",
"details": [
{
"issue": "INVALID_RESOURCE_ID",
"description": "Specified resource ID does not exist. Please check the resource ID and try again."
}
],
...
}
Solution:
-
Double-check the resource ID: Ensure that you are providing the correct resource ID when making the API call. Check for any typos or leading/trailing spaces in the ID.
-
Verify resource existence: Ensure you are accessing a resource ID within 3 hours of its creation. Use the correct Live (Or Sandbox) API endpoints to retrieve information about the resource.
For any additional questions or concerns, contact the PayPal Technical Support team by submitting a ticket from here.
