Skip to main content
POST
Archive organization project
This endpoint requires an Admin Key with the org:write scope, and the key owner must still be an organization admin at call time (otherwise 403 owner_not_admin).

Archive impact and recovery

  • After archiving, inference calls made with the project’s inference API keys are rejected (same semantics as the console); project members and key metadata are preserved.
  • Archiving is one-way: there is currently no unarchive endpoint.
  • Re-archiving is idempotent: archiving an already archived project returns 200 with the current state, without refreshing archived_at or producing another audit event.

Authorizations

Authorization
string
header
required

Send the Admin API secret as a Bearer token in the Authorization header (Bearer sk-admin-***). Create Admin Keys under Console → Organization → Admin API Keys.

Path Parameters

pid
string
required

Project ID.

Response

Archived project.

id
string
required

Project ID.

name
string
required

Project name.

created_at
string<date-time>
required

When the project was created.

description
string

Project description.

archived_at
string<date-time> | null

When the project was archived; null when not archived.

daily_consume_limit
integer<uint64> | null

Daily spend limit (milli-cent); null means unlimited.

Required range: x >= 0
monthly_consume_limit
integer<uint64> | null

Monthly spend limit (milli-cent); null means unlimited.

Required range: x >= 0
max_token_per_minute
integer<uint64> | null

Project-level tokens-per-minute cap (TPM); null clears the project override and inherits the organization rate-limit configuration (not fully unlimited).

Required range: x >= 0