API tokens
An API token lets a script, a pipeline or another system call the Xovris API for your workspace. Create one in the command centre under Settings, Developers.
curl -s -X POST https://api.xovris.ai/v1/tokens \ -H "authorization: Bearer $XOVRIS_TOKEN" -H 'content-type: application/json' \ -d '{"name": "Deploy pipeline", "scopes": ["read"], "expiresInDays": 90}'What every token has
Section titled “What every token has”- A name of 1 to 100 characters, so you know later what uses it.
- Scopes:
read, orreadandwrite. Ask forreadunless the caller changes something. - An expiry between 1 and 365 days, 90 when you do not choose. Tokens that never expire are not issued.
- Its remaining life shown as a meter beside it, so a token close to its end is easy to spot.
For a GitHub workflow, Xovris makes the token and writes it straight into the repository’s Actions secrets itself through the Xovris GitHub App, after you agree once – sealed to that repository, never shown to anyone, never written over a secret already there, and deleted by Xovris again when you remove it. Do it yourself instead: the token’s secret is shown once, when it is created – store it in your secret manager straight away.
Creating one through the API
Section titled “Creating one through the API”POST /v1/tokensContent-Type: application/json
{"name": "Deploy pipeline", "scopes": ["read"], "expiresInDays": 90}An expiry outside 1 to 365 days, or a scope other than read and write, is refused with the reason and what to
send instead.
When a token is no longer needed
Section titled “When a token is no longer needed”Revoke it from Settings, Developers. A revoked or expired token is refused on its next call.
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.