Request logs, response codes and troubleshooting
Interpret logs and resolve methods, credentials, ownership, section, resource, rate, schema and file failures.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Review recent API logs
The administrator page loads recent request logs.
Understand log context
Logs can include key/profile, endpoint/source/module/resource, method, IP and response code.
Understand successful responses
Use the response payload and pagination metadata.
Resolve Bad Request
Check required IDs, fields, section/resource keys and file parameters.
Resolve Unauthorized
Check bearer/session token, expiry, signature and active status.
Resolve Forbidden
Check IP, profile sections, client permissions, ownership, module/resource access and visibility.
Resolve Not Found
Check record, application, document, property, module/resource and safe file path.
Resolve Method Not Allowed
Use the endpoint’s implemented GET or POST method.
Resolve rate limit
Wait for the minute window or adjust allowed rate.
Resolve internal integration errors
Inspect CRM logs, schema, expected module models/tables and safe error evidence.
Resolve schema pending
Deactivate/reactivate the module to run install.php.
Resolve an empty allowed section
Check profile selection, contact permission, ownership and record existence.
Resolve missing adapter output
Check enabled module and compatible schema.
Resolve file upload/download errors
Check 15 MB, extension/MIME, Office container, visibility, ownership and path roots.
Resolve retired legacy endpoint messages
Replace arbitrary client/contact calls with session/me.