Skip to content

Edition Set By Marketplace Plan

URI: https://docs.ankatech.co/errors/edition-set-by-marketplace-plan
HTTP Status: 409 Conflict

When you see this

A write would set the Edition, or the key custody that follows it, of a tenant that a RapidAPI marketplace subscription created. The Edition of such a tenant has one writer: the subscriber's plan. Each request of the subscriber carries its plan, the plan maps to an Edition, and the platform applies that Edition itself, moving the tenant's keys through a key custody window when it already holds keys. A value written beside it would be a second, competing statement of who protects the subscriber's keys, so the write is refused.

The refusal applies to these operations on a marketplace tenant:

Who Operations refused
Platform administrator Assign and clear of the tenant's Edition (assignPlatformTenantEdition, clearPlatformTenantEdition)
Tenant administrator Start, destination, schedule and roll back of a key custody move (createTenantKeyCustodyMove, replaceTenantKeyCustodyMoveDestination, replaceTenantKeyCustodyMoveSchedule, rollbackTenantKeyCustody)
Either plane Declare and bind of a key of the tenant's own (replaceByok, replacePlatformByok, replaceByokDriverDeclaration, replacePlatformByokDriverDeclaration, bindByok, bindPlatformByok)

Operations that set no Edition stay open: the tenant administrator's cancel and abort of a move, the BYOK revert and credential rotation, and the platform administrator's cancel, abort, schedule and roll back of the tenant's key custody move.

Nothing was changed by this request: it is refused before any write, so no Edition, key-encryption key, key declaration or key custody move was written, and no audit row records the refusal.

The Edition read of the tenant reports the same fact before you try: editionSetByMarketplacePlan is true for such a tenant.

Common Causes

  • Assigning an Edition to a marketplace tenant to change its key protection.
  • Clearing the Edition of a marketplace tenant to return it to the deployment Edition.
  • Starting, redirecting, rescheduling or rolling back a key custody move from the marketplace tenant's own plane.
  • Declaring or binding a key of the tenant's own for a marketplace tenant.

Response Example

{
  "type": "https://docs.ankatech.co/errors/edition-set-by-marketplace-plan",
  "title": "Edition set by marketplace plan",
  "status": 409,
  "detail": "The Edition of this tenant is set by its marketplace subscription plan. Nothing was changed.",
  "instance": "/api/v3/admin/platform/tenants/7c9e6679-7425-40de-944b-e07fc1f90ae7/key-backend/edition",
  "timestamp": 1793696400,
  "extensions": {
    "requestId": "9c41e7a2-5b08-4d3f-a6e1-2f7c90b4d815"
  }
}

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

How to Resolve

  1. Leave the Edition to the plan. The subscriber changes its plan on RapidAPI, and the next request it makes under the new plan applies the plan's Edition.
  2. To control a key custody window the plan scheduled, use the tenant's key custody operations instead: a platform administrator may cancel, abort, schedule or roll back the move, and a cancel or a roll back stands. The plan records the move again only after the cooldown, if the subscriber's plan still names another Edition.

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