Skip to Content
SeyloDocs
API referenceInvites

List invites

GET
/api/v1/invites.list

Lists invites, newest first. Pending ones first unless a status is given.

Needs users.view, which owners and admins hold. Not available to MCP clients or the assistant.

Authorization

cookieseylo_session<token>

Query Parameters

status?string|string|string|string

Response Body

Success.

application/json
  1. response
invites*array<>
Example Request
curl -X GET 'https://example.com/api/v1/invites.list'
Example Response
{  "invites": [    {      "id": "string",      "email": "[email protected]",      "role": "admin",      "grants": [        {          "scopeType": "project",          "scopeId": "string",          "scopeName": "string",          "actions": [            "string"          ]        }      ],      "status": "pending",      "invitedBy": {        "id": "string",        "email": "string",        "name": "string"      },      "expiresAt": "2019-08-24T14:15:22Z",      "acceptedAt": "2019-08-24T14:15:22Z",      "createdAt": "2019-08-24T14:15:22Z"    }  ]}

Invite someone POST

Creates an invite link for an email, as an admin or as a member with grants on projects and services. The link is returned once; send it yourself, or it is emailed when the panel has an SMTP channel. An admin invite from a browser session needs a sign-in or auth.reauth from the last 15 minutes (FORBIDDEN details.reason "reauth" otherwise); API keys need none. Needs `users.invite`, which owners and admins hold. Not available to MCP clients or the assistant.

Look at an invite GET

What the accept page shows before anyone signs up: who invited whom, as what, to which projects and services. valid is false for used, revoked, expired or unknown tokens. Needs no sign-in. Not available to MCP clients or the assistant.