Skip to content

Marketplace Credential Unavailable

URI: https://docs.ankatech.co/errors/marketplace-credential-unavailable
HTTP Status: 503 Service Unavailable

When you see this

The request came through the RapidAPI marketplace, and the platform could not read the shared credential it uses to recognize the RapidAPI gateway. Without that credential the request cannot be judged either way, so it is refused before any processing. This is an availability fault on the platform side, not an authentication failure: a wrong gateway credential is answered 401, never this.

Two services answer this cause, with the same type, title, detail, status and Retry-After: 30:

  • The cryptographic API — every request carrying the X-RapidAPI-Proxy-Secret header on a SaaS deployment with the marketplace enabled.
  • The authentication API — only where its own RapidAPI filter is enabled (it is off by default), for a request carrying its configured marketplace header (default x-rapidapi-key) on a path that requires authentication. On the token, logout and other public paths it does not refuse: the request continues without marketplace authority.

Common Causes

  • The marketplace credential has not been written in the Admin Console yet.
  • The platform's deployment-secret service is temporarily unreachable from the service that received the request.

Response Example

{
  "type": "https://docs.ankatech.co/errors/marketplace-credential-unavailable",
  "title": "Marketplace credential unavailable",
  "status": 503,
  "detail": "The RapidAPI marketplace credential could not be resolved from the deployment custody plane. Marketplace ingress is unavailable; this is not an authentication failure.",
  "instance": "/api/v3/crypto/encrypt",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000,
  "extensions": { "code": "SERVICE_UNAVAILABLE" }
}

The example is the cryptographic API's body. The authentication API's body carries the same type, title, status and detail, and carries no correlation id in the body (its correlation id is in the X-Correlation-Id response header).

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Retry after the delay in the Retry-After header (30 seconds).
  2. If you operate the deployment, confirm the RapidAPI proxy secret is written in the Admin Console and that the deployment-secret service is reachable.
  3. Contact support if the refusal persists.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.