Teams API

Manage teams and membership. Requests remain subject to your account and team permissions.

Use API authentication for protected requests. Examples use your own resource IDs and a temporary token; saved response examples are synthetic.

Method	Path	Operation
`GET`	`/v1/team`	List teams
`POST`	`/v1/team`	Create team
`GET`	`/v1/team/{id}`	Get team
`PUT`	`/v1/team/{id}`	Update team
`DELETE`	`/v1/team/{id}`	Delete team
`GET`	`/v1/team/deployment-context`	Get deployment context
`GET`	`/v1/team/members`	List team members
`GET`	`/v1/team/invitations`	List team invitations
`POST`	`/v1/team/invitations`	Invite a team member
`POST`	`/v1/team/invitations/{id}/resend`	Resend team invitation
`DELETE`	`/v1/team/invitations/{id}`	Revoke team invitation

List teams

GET /v1/team

Returns a paginated list of Team

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.
`page`	query	no	Page number
`per_page`	query	no	Items per page

Request example

Set ADIOS_API_URL=https://api.adios.dev. For protected requests, set ADIOS_ACCESS_TOKEN and ADIOS_TEAM_ID as in the quickstart. Set any additional ADIOS_* variables from your own resource results.

curl --fail-with-body --request GET "$ADIOS_API_URL/v1/team" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

List of Team

Response fields

Field	Type	Description
`data`	array
`data[].created_at`	integer	(Unix timestamp)
`data[].deleted_at`	integer	(Unix timestamp)
`data[].description`	string
`data[].owner_id`	string
`data[].parent_id`	string
`data[].status`	string	Allowed: active, inactive, suspended, deleted.
`data[].team_id`	string
`data[].title`	string
`data[].updated_at`	integer	(Unix timestamp)
`pagination`	object
`pagination.page`	integer	Current page number
`pagination.per_page`	integer	Number of items per page
`pagination.total`	integer	Total number of items

Illustrative example; not a live response:

{
  "data": [
    {
      "created_at": 1791072000,
      "deleted_at": 0,
      "description": "",
      "owner_id": "000000000000000000000000001",
      "parent_id": "000000000000000000000000001",
      "status": "active",
      "team_id": "000000000000000000000000001",
      "title": "Postman example",
      "updated_at": 1791072000
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 1,
    "total": 1
  }
}

Create team

POST /v1/team

Creates a new Team

This request changes data or starts an action. Review the target and body before sending it.

Request fields (the body contains an editable example):

Field	Type	Required	Description
`description`	string	no	Default: `""`.
`owner_id`	string	yes
`parent_id`	string	no
`status`	string	yes	Allowed: active, inactive, suspended, deleted. Default: `"active"`.
`title`	string	yes

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request POST "$ADIOS_API_URL/v1/team" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "owner_id": "YOUR_USER_ID",
  "title": "Postman example team",
  "status": "active"
}
JSON

Replace YOUR_* body placeholders before sending. The quoted heredoc keeps the JSON literal.

Response: HTTP 201

Team created

Response fields

Field	Type	Description
`created_at`	integer	(Unix timestamp)
`deleted_at`	integer	(Unix timestamp)
`description`	string
`owner_id`	string
`parent_id`	string
`status`	string	Allowed: active, inactive, suspended, deleted.
`team_id`	string
`title`	string
`updated_at`	integer	(Unix timestamp)

Illustrative example; not a live response:

{
  "created_at": 1791072000,
  "deleted_at": 0,
  "description": "",
  "owner_id": "000000000000000000000000001",
  "parent_id": "000000000000000000000000001",
  "status": "active",
  "team_id": "000000000000000000000000001",
  "title": "Postman example",
  "updated_at": 1791072000
}

Get team

GET /v1/team/{id}

Returns a single Team

Set team_id using IDs from your own API responses.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`id`	path	yes	Resource identifier from your team's API results.
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request GET "$ADIOS_API_URL/v1/team/${ADIOS_TEAM_ID}" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Team

Response fields

Field	Type	Description
`created_at`	integer	(Unix timestamp)
`deleted_at`	integer	(Unix timestamp)
`description`	string
`owner_id`	string
`parent_id`	string
`status`	string	Allowed: active, inactive, suspended, deleted.
`team_id`	string
`title`	string
`updated_at`	integer	(Unix timestamp)

Illustrative example; not a live response:

{
  "created_at": 1791072000,
  "deleted_at": 0,
  "description": "",
  "owner_id": "000000000000000000000000001",
  "parent_id": "000000000000000000000000001",
  "status": "active",
  "team_id": "000000000000000000000000001",
  "title": "Postman example",
  "updated_at": 1791072000
}

Update team

PUT /v1/team/{id}

Updates an existing Team

Set team_id using IDs from your own API responses.

This request changes data or starts an action. Review the target and body before sending it.

Request fields (the body contains an editable example):

Field	Type	Required	Description
`description`	string	no	Default: `""`.
`owner_id`	string	yes
`parent_id`	string	no
`status`	string	yes	Allowed: active, inactive, suspended, deleted. Default: `"active"`.
`title`	string	yes

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`id`	path	yes	Resource identifier from your team's API results.
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request PUT "$ADIOS_API_URL/v1/team/${ADIOS_TEAM_ID}" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "owner_id": "YOUR_USER_ID",
  "title": "Postman example team",
  "status": "active"
}
JSON

Replace YOUR_* body placeholders before sending. The quoted heredoc keeps the JSON literal.

Response: HTTP 200

Team updated

Response fields

Field	Type	Description
`created_at`	integer	(Unix timestamp)
`deleted_at`	integer	(Unix timestamp)
`description`	string
`owner_id`	string
`parent_id`	string
`status`	string	Allowed: active, inactive, suspended, deleted.
`team_id`	string
`title`	string
`updated_at`	integer	(Unix timestamp)

Illustrative example; not a live response:

{
  "created_at": 1791072000,
  "deleted_at": 0,
  "description": "",
  "owner_id": "000000000000000000000000001",
  "parent_id": "000000000000000000000000001",
  "status": "active",
  "team_id": "000000000000000000000000001",
  "title": "Postman example",
  "updated_at": 1791072000
}

Delete team

DELETE /v1/team/{id}

Deletes a Team

Set team_id using IDs from your own API responses.

This request changes data or starts an action. Review the target and body before sending it.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`id`	path	yes	Resource identifier from your team's API results.
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request DELETE "$ADIOS_API_URL/v1/team/${ADIOS_TEAM_ID}" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Resource deleted.

Response fields

Field	Type	Description
`message`	string

Illustrative example; not a live response:

{
  "message": "Deleted successfully"
}

Get deployment context

GET /v1/team/deployment-context

Discover available deployment regions and the active team deployment context.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request GET "$ADIOS_API_URL/v1/team/deployment-context" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.

List team members

GET /v1/team/members

List members of the selected team.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request GET "$ADIOS_API_URL/v1/team/members" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.

List team invitations

GET /v1/team/invitations

List invitations for the selected team.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request GET "$ADIOS_API_URL/v1/team/invitations" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.

Invite a team member

POST /v1/team/invitations

Send an email invitation to join the selected team. role supports user, manager, or team_admin.

This request changes data or starts an action. Review the target and body before sending it.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request POST "$ADIOS_API_URL/v1/team/invitations" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "email": "YOUR_INVITE_EMAIL",
  "role": "user"
}
JSON

Replace YOUR_* body placeholders before sending. The quoted heredoc keeps the JSON literal.

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.

Resend team invitation

POST /v1/team/invitations/{id}/resend

Send the invitation email again.

Set invitation_id using IDs from your own API responses.

This request changes data or starts an action. Review the target and body before sending it.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`id`	path	yes	Resource identifier from your team's API results.
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request POST "$ADIOS_API_URL/v1/team/invitations/${ADIOS_INVITATION_ID}/resend" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.

Revoke team invitation

DELETE /v1/team/invitations/{id}

Revoke a pending invitation.

Set invitation_id using IDs from your own API responses.

This request changes data or starts an action. Review the target and body before sending it.

Authentication: bearer token and the team header shown below.

Parameters

Name	Location	Required	Description
`id`	path	yes	Resource identifier from your team's API results.
`X-Tenant-ID`	header	yes	Active team ID. Must match the tenant bound to a diagnostic token.

Request example

curl --fail-with-body --request DELETE "$ADIOS_API_URL/v1/team/invitations/${ADIOS_INVITATION_ID}" \
  -H "Authorization: Bearer $ADIOS_ACCESS_TOKEN" \
  -H "X-Tenant-ID: $ADIOS_TEAM_ID"

Response: HTTP 200

Successful response. Inspect returned state for operations that start asynchronous work.

A complete response-body schema is not published for this custom operation. Inspect the returned content and status; no payload is assumed here.