Browse documentation
← API reference

invites

Invites that wait

GET /api/v1/invites

Lists pending organization invitations. Organization owners read pending invitations by supplying org. Newest first.

Parameters

orgquery · required · string

The organization whose pending invitations to read.

Example request

curl --request GET 'https://commitscale.com/api/v1/invites?org=acme' \
  --header "Authorization: Bearer $CSCALE_TOKEN"

Example values illustrate the format. Use your own credentials and identifiers.

Responses

200 The invites that wait.

application/json

{
  "invites": [
    {
      "created_at": "2026-10-26T10:00:00Z",
      "email": "person@example.com",
      "expires_at": "2026-10-26T10:00:00Z",
      "id": 1,
      "invited_by": "user:alex",
      "org": "acme",
      "person": "user:alex"
    }
  ]
}

invitesrequired · array of object

Invitations visible to the caller.

Fields of invites

Invitations visible to the caller.

Each item has this shape.

An invite that waits for its person.

created_atrequired · string (date-time)

When this record was created, in UTC.

emailoptional · string

The address it went to, for an invite sent to an address. An invite to someone by their handle never shows their address.

expires_atrequired · string (date-time)

Its link works until then.

idrequired · integer (int64)

Identifier used to accept, decline or withdraw the invitation.

invited_byrequired · string

Who sent it, such as user:john.

orgoptional · string

The organization's namespace name, such as acme.

personoptional · string

The person it is for, such as user:carol, for an invite sent to them by their handle.

roleoptional · owner / member

The person's role in the organization: owner or member.

RateLimit and RateLimit-Policy describe the request rate. Follow Retry-After when a response asks you to wait.

Problem responses

Errors use application/problem+json. Act on the stable code, and follow next when present. See the problem format.

check_key_scope403

A check-only key may call the test check, read its own usage and acceptance rule, contact support, and withdraw data sharing.

Use a person's sign-in for account management. More agent power needs the owner's passkey; this key cannot widen itself.

feature_off403

The namespace plan does not include this feature.

Retrying on the same plan will not help. GET /api/v1/namespaces/{namespace}/plan, and the namespace's Plan page in Settings, show what its plan includes.

unauthenticated401

The request carried no credentials.

Use this operation's sign-in method. Bearer credentials use Authorization: Bearer <token>; browser credentials use the session cookie.

invalid_token401

The token is unknown, expired, or revoked, its agent was revoked, or an OAuth token was used outside its MCP resource.

Stop using it. Sign in again, or ask the owner to create a replacement agent key.

forbidden403

The caller may not do this: only people may, only owners may, or the agent was not given this repository or write access.

Stop. Retrying will not help. Ask the owner for the access, or leave the step to a person.

not_found404

It does not exist, or the caller cannot read it: a repository the caller cannot read is reported as not found.

Check the name or ID, and that the token has the repository.

invalid_request400

The request is malformed or breaks a rule, such as a title that is too long, or a body that is not the expected JSON.

Fix the request as detail says. The same request fails the same way.

quota_exceeded429

With 429, the caller used its requests for the minute. With 422, a count limit was reached.

With 429, wait Retry-After seconds and retry. With 422, remove one first.

internal500

The server failed, and logged why.

Retry after Retry-After seconds. A write is safe to retry with the same idempotency key.