Get started¶

Before you start¶

You need an account before any of this works

Every step below depends on having an identity in the Taiga Cloud identity provider. There is no self-registration — accounts cannot be created from these docs, from the API, or by signing up.

Access is granted by invitation. Someone who already administers the customer or project invites you, and you accept that invitation to activate your account. If you do not have one yet:

Your organisation already uses Taiga Cloud — ask whoever administers your customer or project to invite you. They can do it from the portal.
Your organisation is new to Taiga Cloud — talk to us first. Contact sales in the Help menu above.
You had access and lost it — your invitation may have expired or your role may have been removed. Support in the Help menu.

Until then the approval step in the device code flow has nothing to approve against, and it will fail rather than prompting you to register.

1. Get a token¶

Follow Authentication to run the OAuth flow and obtain a bearer token.

If you only want to try an endpoint, skip it — /reference has a Sign in button that does the whole flow and attaches the token to requests you send from the page.

2. Find the endpoint¶

Browse /reference. It is generated from the running service, so it always matches what is deployed. Endpoints needing authentication are marked with a padlock.

3. Call it¶

curl -H "Authorization: Bearer $TOKEN" \
  https://<<INSERT API URL>>/v2/projects

The base API url can be found at the top of /reference. Start with /v2/projects — it shows which projects your role covers, which determines what everything else will return.

If something comes back unexpected¶


`401`	The token is missing, expired or malformed. Get a new one.
`403`	You are authenticated, but your role does not permit the action.
`404`	Either it does not exist, or it is outside your scope.

The full list, and what each endpoint can return, is in /reference.