Skip to main content
POST
Approve community mirror proposal

Authorizations

Authorization
string
header
required

Bearer token in the Authorization header. Two token types are accepted:

  • Organization API key (sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use.
  • User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at /.well-known/oauth-authorization-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.

Path Parameters

id
string<uuid>
required

Body

application/json
proposal_digest
string
required

SHA-256 digest that reviewers must echo when approving or rejecting this exact revision.

Pattern: ^[a-f0-9]{64}$
review_notes
string
Maximum string length: 2000

Response

Proposal approved and mirror published

success
enum<boolean>
required
Available options:
true
platform
string
required

Lowercase platform identifier, normalized by the service.

Pattern: ^[a-z0-9_-]{1,64}$
Example:

"example_platform"

catalog_etag
string | null
required
superseded_by
string | null
required

HTTPS successor document URL, when this mirror has been superseded.

Pattern: ^https:\/\/
publisher_domains
string[]
required

Publisher domains updated from this community mirror catalog.

updated_at
string<date-time>
required
proposal_id
string<uuid>
required

Opaque identifier for the proposal.

Example:

"4ec8bc86-6180-4d0e-aa72-9cbf402d3638"