Org

Invite a member by email (owner-only + step-up)

If the email already maps to a principal they are added active; otherwise a pending invited membership is created and claimed at first login. Creating (or re-POSTing) a pending invite sends a notification email to the invitee — re-invite is resend, rate-limited to one send per (org, email) per 5 minutes. The email is a notification, not a token: signing in with the invited email is the acceptance.

post/orgs/v1/{org_id}/invites

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/orgs/v1/{org_id}/invites
  • Auth: one of:
    • API key in header SIGN-IN-WITH-X
    • HTTP bearer

Path parameters

org_idstring uuid required

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Request body

emailstring email required
role'owner' | 'admin' | 'developer' | 'billing' | 'viewer'
invite_ttl_hoursinteger

Response

Invited or added

status'invited' | 'added'
principal_idstring uuid
role'owner' | 'admin' | 'developer' | 'billing' | 'viewer'
email_sentboolean

Present only for status=invited. Whether a notification email was sent on this request — false when the resend was rate-limited (one send per org+email per 5 minutes) or delivery failed; the pending invite is live either way and is accepted by signing in with the invited email.

Changes

No recorded changes to this operation across all 1 revision of this API.