Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

Revoke a pending invitation

DELETE

/v1/members/invitations/{id}

const url = 'http://localhost:8080/v1/members/invitations/example';
const options = {
  method: 'DELETE',
  headers: {cookie: 'hardcount_session=<hardcount_session>'}
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url http://localhost:8080/v1/members/invitations/example \
  --cookie hardcount_session=<hardcount_session>

Stamps the invitation revoked; its accept link stops working immediately (revoke racing an accept: exactly one wins). Only pending invitations can be revoked — accepted/revoked ones 404.

Authorizations

SessionCookie

Parameters

Path Parameters

required

string

Responses

204

Invitation revoked

404

No pending invitation with this id (code not_found).

application/json

object

error

object

type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string

code

string

message

string

request_id

string

param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
  "error": {
    "type": "invalid_request_error"
  }
}