Error Codes
Errors are returned as { "code": "…", "message": "…" }.
Request errors
Section titled “Request errors”| Code | HTTP | Meaning |
|---|---|---|
meta-file-or-path-not-found | 404 | The requested file or path does not exist in the repository |
meta-path-type-not-supported | 400 | The path type is not serveable |
meta-unknown-operation-type | 400 | Unknown type/operation in the request |
meta-unknown-service-name | 400 | The named service has no folder mapping |
META_MISSING_CUSTOMER | 400 | No X-Customer header and no customer claim in the JWT |
META_READONLY | 403 | Write attempted against a read-only repository |
META_NOT_LOCAL | 400 | Git porcelain operation attempted against a non-local repository |
| — (version) | 400 | ?version= is outside the repository’s allowedversions |
| — (entitlement / access) | 403 | Blocked by the repository’s access rule or a missing license entitlement |
Operational errors
Section titled “Operational errors”| Code | HTTP | Meaning |
|---|---|---|
meta-config-client-not-found | 503 | Config client unavailable at request time |
meta-forge-url-not-found | 500 | Authoring source URL not configured |
meta-forge-product-request-failed | 502 | Upstream authoring source rejected the request |
meta-indexer-contenttype-not-found | 500 | No content parser for the indexed type |
meta-internal-server-error | 500 | Unexpected server error |
See also Operations → Failure modes.