Resource Not Found

Cause: Requested resource doesn't exist or you don't have permission to access it.

Suggested Action: Verify the resource ID in your request URL. Check if the resource was deleted or if you have correct access permissions.

Common Scenarios:

• Invalid or non-existent resource ID
• Accessing deleted leads or users or datasets
• Incorrect endpoint path or version
• Permission-based resource restrictions

Response Example

{
  "type": "https://developers.leadboxer.com/docs/resource-not-found",
  "title": "Resource Not Found",
  "status": 404,
  "detail": "The requested key with ID 12345 does not exist",
  "instance": "/v1/users/12345"
}

HTTP Status

404 Not Found

Troubleshooting

• Double-check resource IDs in URLs
• Verify resource exists in LeadBoxer web interface
• Ensure you're using correct API endpoint version
• Check user permissions for resource access