ERP.AI
Find the cause of an API access problem.
Check one boundary at a time so an access problem does not turn into an unnecessary change to roles or business data.
Capture the smallest useful diagnostic.
Record the environment, operation, response status, and redacted error body. Include the request path and relevant non-secret parameters. Keep the bearer credential, private record content, and personal data out of screenshots and shared logs.
Compare the request with the current platform or installed skill reference. Confirm that it targets the authenticated API origin, not the marketing website or an origin copied from a different environment.
Work through the likely boundaries.
| Symptom | What to check |
|---|---|
| HTML instead of an API response | Check the host and path against the current environment’s API reference; a website or sign-in page may have answered the request. |
| Authentication rejected | Confirm the supported bearer format, the configured credential, and whether the credential remains valid in this environment. |
| Access denied | Review the caller’s organization, app access, assigned role, and requested operation before broadening permissions. |
| App or resource not found | Resolve the actual installed app and resource identifiers through authenticated discovery; do not substitute the catalogue slug. |
| Request rejected by validation | Inspect required fields, identifiers, relationships, allowed values, and the current schema. |
| Intermittent limits or service failures | Check documented limits and retry guidance; use bounded retries and inspect the final result. |
Reduce the request without changing the business.
Try a documented, narrow read that the caller is expected to perform. Confirm the app and schema before retrying a more complex action. If a read works but a write fails, investigate the operation’s permission and validation requirements separately.
Do not respond to an unexplained failure by granting broad administrative access or repeatedly submitting a write. A previous attempt may have reached the owning service even when the client did not receive a useful response.
Escalate with a reproducible, redacted example.
Provide the environment, intended operation, observed result, timestamp, and a minimal request example with secrets removed. Include a request or correlation identifier if the response provides one. Explain what changed before the failure and which read-only checks succeeded.
Put ERP.AI to work for your business.
Choose an application, then configure the records, roles and workflows your team needs.