List Organization Invitations
Request
GET
https://api.sourcecraft.tech/orgs/{org_slug}/invites
Path parameters
|
Name |
Description |
|
org_slug |
Type: string Example: `` |
Query parameters
|
Name |
Description |
|
org_id |
Type: string Example: `` |
|
page_size |
Type: string<uint64> The maximum number of repositories to return. The service may return fewer than Example: `` |
|
page_token |
Type: string A page token, received from a previous call. When paginating, all other parameters must match Example: `` |
Responses
200 OK
A successful response.
Body
application/json
{
"invites": [
{
"id": "example",
"email": "example",
"alias": "example",
"invite_link": "example",
"invitee": {
"id": "example",
"slug": "example"
},
"status": "creating",
"subject": {
"type": "user",
"id": "example"
},
"created_at": "2025-01-01T00:00:00Z",
"expires_at": "2025-01-01T00:00:00Z"
}
],
"next_page_token": "example"
}
|
Name |
Description |
|
invites |
Type: Invite[] Example
|
|
next_page_token |
Type: string A token, which can be sent as Example: |
UserEmbedded
|
Name |
Description |
|
id |
Type: string Example: |
|
slug |
Type: string Example: |
Example
{
"id": "example",
"slug": "example"
}
InviteStatus
Type: string
Enum: creating, pending, accepted, rejected
SubjectType
Type: string
Enum: user, invitee, team
Subject
|
Name |
Description |
|
id |
Type: string Example: |
|
type |
Type: SubjectType Enum: |
Example
{
"type": "user",
"id": "example"
}
Invite
Invite represents an organization invitation.
Exactly one of email, alias, or invitee is set depending on invite type.
|
Name |
Description |
|
alias |
Type: string Example: |
|
created_at |
Type: string<date-time> Example: |
|
|
Type: string Example: |
|
expires_at |
Type: string<date-time> Example: |
|
id |
Type: string Example: |
|
invite_link |
Type: string Example: |
|
invitee |
Type: UserEmbedded Example
|
|
status |
Type: InviteStatus Enum: |
|
subject |
Type: Subject Example
|
Example
{
"id": "example",
"email": "example",
"alias": "example",
"invite_link": "example",
"invitee": {
"id": "example",
"slug": "example"
},
"status": "creating",
"subject": {
"type": "user",
"id": "example"
},
"created_at": "2025-01-01T00:00:00Z",
"expires_at": "2025-01-01T00:00:00Z"
}
default
Both Client Errors (4xx) and Server Errors (5xx) are serialized into this scheme
Body
application/json
{
"error_code": "example",
"message": "example",
"request_id": "example",
"details": {}
}
|
Name |
Description |
||
|
details |
Type: Optional details. Exact structure depends on error_code
Example
|
||
|
error_code |
Type: string Example: |
||
|
message |
Type: string Example: |
||
|
request_id |
Type: string Example: |