Authentication

The base URL is https://api.ellipsis.dev. Every endpoint lives under the /v1 prefix.

Create an API key under Platform → API keys in the Ellipsis dashboard. The secret starts with ellipsis_key_ and is shown only once, so copy it when you create it. API keys authenticate scripts and automations as your organization; the CLI instead uses a user token that agent login mints for you, which acts as you personally. Both are sent the same way.

Store the key in an environment variable rather than committing it. ELLIPSIS_API_TOKEN is the name the CLI reads too, so one variable serves both:

export ELLIPSIS_API_TOKEN="ellipsis_key_..."

Send the key as a bearer token on every request. An invalid key is rejected with 401.

curl https://api.ellipsis.dev/v1/me \
  -H "Authorization: Bearer $ELLIPSIS_API_TOKEN"

{
  "customer_id": "cust_8Rn4wY7kQm2v",
  "customer_login": "your-org",
  "user_id": null,
  "gh_user": null,
  "api_key_id": "tokens_api_9Qz3vT6wLm2r",
  "sandbox_id": null
}

GET /v1/me returns who the credential is: an API key acts as the organization, so user_id and gh_user are null; a user token fills them with the developer behind it.