Marketplace state reference

Treat these lowercase values as the current repository contract. Do not build against unimplemented state names.

Developer states

active, suspended

Developer suspension invalidates derived installation authority. Old codes, tokens and subscriptions cannot regain authority merely because a developer is reactivated.

App states

draft, submitted, approved, published, rejected, suspended

Public discovery requires publication conditions. Public listing metadata is read from the reviewed, version-scoped snapshot selected by the app's active listing pointer. Reviewed submitted, approved, and published snapshots cannot be silently edited in place.

Version states

draft, submitted, approved, published, rejected, suspended

Review is per exact version. Publication is serialized, and the active listing pointer can reference only the app's current reviewed publication. Installation is pinned to the selected published version and granted scopes; publishing a replacement does not move either automatically.

Legacy records whose reviewed listing provenance cannot be proven fail closed as legacy_unverified. A legacy submitted version can only be rejected by Super Admin. Its owning developer must then provide a complete replacement draft and resubmit it through the normal review lifecycle. The legacy data is never treated as reviewed merely because it was migrated.

Installation states

active, revoked

Revocation clears granted scopes and records uninstall time. Codes, tokens and subscriptions bind to the exact installed reviewed version and generation; reinstall requires fresh authority. A newer publication does not change the installed version automatically.

Webhook delivery states

pending, processing, delivered, failed, dead

A failed delivery may be retried within the bounded attempt policy. dead is terminal for that delivery. Queue claims, one-use admission and completion enforce revocation. Already admitted network requests cannot be recalled; receivers still need replay protection.

Not current

in_review, changes_required, and retired are not current values. Do not send, store, display, or branch on them as if the platform supports them.