Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

This guide steps you through the basics of getting up and running with the Tanda API. We'll cover how to connect to your account, how to get some data out, and how to put some data in. The API does a lot and we encourage you to read the docs for a complete list of functionality - this is just a quick intro to some basic concepts.

To test the API, we highly recommend Postman, a tool for working with APIs. There will be some example Postman screenshots in this guide. The API documentation includes sample curl statements, and there's code samples in various other languages on GitHub. But the cool thing about Postman is that there's no programming knowledge required for this guide.

0. Glossary

A few terms you'll see in this guide, that you might have seen before:

  • Request - in HTTP, a message sent from one system to another (in this case, from your code, to the API)
  • Response - what a web server sends back when you send it a request
  • Endpoint - a particular URL that the API responds to
  • GET, POST, PUT, DELETE - HTTP methods. GET means "give me data". POST means "insert this data". PUT means "update with this data". DELETE means "get rid of data".

1. Getting authenticated

The first step to working with the API is to get an access token. An access token is a random series of letters and numbers used to uniquely identify you. You need to provide it with every request you make to the API.

To get an access token, go to (you'll need to be logged in to Tanda). You'll need to choose which scopes you want. Scopes let you control which parts of the API you can access. For this example we are just going to look at User data so we just need the me and user scopes - but if you are just playing around with the API there's no real harm in ticking all scopes.

creating a new token

Once you click save token, you will see your newly created access token. You must copy and paste this access token somewhere safe, because you'll only be able to see it once. This access token is valid forever - if you want to disable it, you can always delete it later by coming back to and clicking delete token.

reading a new token

To use this access token, you'll have to set a custom header on each request. In Postman, this looks like this: (make sure you spell "Authorization" and "Bearer" correctly!)

setting a header in Postman

2. Getting data

Now that you have an access token, you can use it to query the API. Let's start by getting a list of staff.

In the API documentation, we find the appropriate endpoint: Users. It says we need to make a GET to /api/v2/users. That's easy in Postman:

postman - making a get

The response will be JSON formatted, which is handy because it's easy for humans to read, but also can easily be parsed by most programming languages. For every endpoint in the API, the documentation includes an example JSON response in the right sidebar.

API doc example

3. Posting (creating) data

Let's try adding a new employee into Tanda. To do this, we want the "Create User" endpoint in the API documentation. This endpoint says we should make a POST to /api/v2/users. Let's do that in Postman. According to the API documentation, only the name field is required - but we're going to enter a few other fields too, just to play with different data types.

postman - making a post

Send this request, and the API will return a complete employee record:

postman - post response

You'll also be able to see the newly created employee inside Tanda - in this case, by going to Unless it says so in the documentation, all API methods make changes to Tanda instantly, so you can always check that your API call has worked by checking on the Tanda site.

4. Putting (editing) data

Let's say we got that employee's name wrong. We can easily change that using the API. The API method to edit things is PUT (doc), and when you're editing things, you need to include the ID of the object you'd like to edit.

When we created Danny's profile in Tanda in the posting section just above, the JSON response we got back included his ID. But if we don't have that handy, we can also find his ID by GETting a list of users and finding him in the list that's returned. In this example, his ID is 155464. So, if we want to edit Danny's details, we would make a PUT to /api/v2/users/155464. When PUTing, we only need to include the fields we want to change:

postman - making a put

As you can see, IDs are pretty important - by knowing Danny's ID we were able to make other changes to his record. In Tanda, everything has an ID, and you'll use this ID to make changes or delete things. Often, the API code you're writing will be keeping data in sync between another system you use and Tanda. It will make your API life much easier if you keep a mapping of IDs between the two systems somewhere. So for example, if you have another system with staff data that you are going to import into Tanda, then you should keep a mapping between unique IDs in that system, and the corresponding user IDs in Tanda.

5. What's next?

Hopefully this intro has given you a better understanding of the sorts of things you can do with the Tanda API. Our API is comprehensive - anything you can do in Tanda just by clicking around, you can also do (much faster) using the API. Next up, have a read of the documentation - the left sidebar contains a list of different endpoints that represent different things you can do. If you'd like help designing or scoping your API integration, get in touch and our solution architects can get you up and running.