Skip to main content
GET
/
v0
/
organisation
/
{org_id}
/
keys
/
{key_id}
Get API key details
curl --request GET \
  --url https://sis.sumvin.com/v0/organisation/{org_id}/keys/{key_id} \
  --header 'Authorization: Bearer <token>'
{
  "_links": {
    "self": {
      "href": "<string>",
      "method": "GET",
      "templated": false,
      "description": "<string>"
    },
    "organisation": {
      "href": "<string>",
      "method": "GET",
      "templated": false,
      "description": "<string>"
    }
  },
  "api_key": {
    "id": "<string>",
    "name": "<string>",
    "created_at": 123,
    "enabled": true,
    "scopes": [
      "<string>"
    ],
    "env_id": "<string>"
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
org_id
string
required
​
key_id
string
required

Response

Successful Response

​
_links
OrgChildLinks · object
required
​
api_key
APIKeyData · object
required

A single API key in the listing.

partition is derived from the key's scope namespace prefix at every read — "public" for rpc.*, "server" for sis.*. Keys with no scopes, all-unknown namespaces, or cross-partition scopes surface partition=None; the dashboard renders those as an "unknown" badge so a human can investigate. scopes carries the full Unkey permission list so the dashboard can filter / display without a round-trip. The org-mintable scope vocabulary is sis.lookup, sis.get_details, sis.get_kyc, sis.token_exchange, sis.get_pints, rpc.invoke; platform-only scopes (sis.rpc_usage, sis.rpc_sponsorship) and worker-only scopes (internal.invoke) may also appear on keys granted out-of-band and are surfaced verbatim. env_id is the persisted environment binding from meta.env_id; keys without a binding surface None.