Authentication
Requests to the Wisps API use a team token in the Authorization header:
Authorization: Bearer <WISPS_TOKEN>Get a token
Section titled “Get a token”If your provider offers account sign-in, install the CLI from the public releases, then sign in:
wisp login --api https://api.example.comCreate an API token for your application or agent:
wisp tokens create sandbox-appStore the returned token securely as WISPS_TOKEN. If your provider does not offer account sign-in, ask them for a team token and API URL.
Token permissions
Section titled “Token permissions”| Token | Use |
|---|---|
| Team API token | Application and agent access; may create and keep only ephemeral wisps |
| Person’s team token | Interactive use; may also create on-demand and always wisps |
An API token requesting a persistent mode receives HTTP 403. A user account token is for account operations and cannot replace a team token on the Wisps API.
Protect credentials
Section titled “Protect credentials”Keep tokens outside the wisp and outside browser application code. The TypeScript SDK runs in Node, not the browser. Never put tokens in URLs or commit them with examples.
A request for another team’s wisp returns HTTP 404, the same as a missing wisp. See API errors.