Quick start API

Start with API health, then verify your bearer token and team context.

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/health	Check API health
GET	/v1/auth/me	Get current user

Check API health

GET /v1/health

Check whether the API process is responding.

Authentication: public; no bearer token required.

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/health"

Response: HTTP 200

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

Illustrative example; not a live response:

{
  "status": "ok"
}

Get current user

GET /v1/auth/me

Return your user_id, profile, teams, and team_data. The response script saves only user_id in the selected environment. Set team_id yourself to the active CLI team before using a diagnostic token.

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

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/auth/me" \
  -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.