Skip to main content

Frequently asked questions about the Semble API

Jessica Magri avatar
Written by Jessica Magri
Updated over a week ago

This article is for software developers and IT admins who want to integrate the Semble Public API into their own systems. Our updated API reference can be found here.

Select a section or question from the following list to find out more about the Semble API:


What role does a user need to be assigned as to use the Semble API?

To use the Semble API, a user needs to be assigned the Manager role or any custom role which allows API access. Ensure that the appropriate role is assigned to any user who requires API access.

Can Semble help our practice build a bespoke API solution?

Semble does not build bespoke solutions for practices, however we do know
that a number of our clients have used other third-party organisations to
successfully assist them with their software development.

Contact our Customer Success team at for more information.

Note: Semble accepts no responsibility or liability for the goods
and services provided by third-party companies.

Signing in

How do I sign into the Semble API server?

To sign in, you must generate an authentication token and update your HTTP headers. For more information, see here.

Where do I find my API key?

Users can generate their own API tokens. This can be done directly from the API Access tab within Semble.

How long does my authentication token last for?

Authentication tokens last for 12 hours. It is recommended that you sign in at the start of every day.

About the Semble API

Why does the Semble API use GraphQL?

GraphQL (GQL) is rapidly becoming the API standard across many software development landscapes. Here are a few reasons why GQL is becoming more popular:

  • Allows clients to specify exactly what they want from a server, without any risk of over-fetching nor under-fetching data

  • GQL is very flexible, meaning that changes on the client do not require any extra work on the server

  • You can retrieve many resources in a single request. REST APIs typically require loading from multiple URLs, whereas with GQL you can get all the data your app needs in a single request

  • GQL APIs are organised in types and fields rather than endpoints. This ensures that apps only ask for what is possible, and can provide clear and helpful errors

  • You can still integrate legacy REST systems with GQL APIs

If you want to learn more about the benefits of GQL, you can visit the official GQL website here.

What data is available with the Semble API?

You can create, read, update, and delete data from most collections such as:

  • Availability

  • Patients

  • Contacts

  • Bookings

  • Invoices

  • Letters

For a full list of what is available from the Semble API, see here.

What data is not available with the Semble API?

The Semble API library is being constantly expanded on, however there are some collections that are not yet available:

  • Tasks

  • Questionnaires (create)

  • Records (create, update, delete)

For a full list of what is available from the Semble API, see here.

What is the Semble API request limit?

At the moment you can send the Semble API 240 requests per minute. However this is soon being reduced to 120 requests per minute.

How are actions performed using the API displayed in the logs of the UI?

Every action using the Semble API is added in the logs, with the account name who performed them displayed as well.

Did this answer your question?