The Kinabase API

The Kinabase API lets approved external systems work with your organisation’s records

, collections

Collection

A container for records in Kinabase, similar to a table in a spreadsheet or database, used to organise one type of data such as Projects or Contacts.

, colleagues

Colleague

Someone in your organisation with a Kinabase account; the built-in Colleagues list is where their profiles are managed.

and other data. System admins control which integrations are registered and whether they can connect. A developer or implementation partner should complete the technical setup.

---

1. What you can do with the API

Read and write records

Find, add and update records, including groups of records, and move them through workflow stages.

Look up your data model

View how your collections are structured so an integration can use the right information.

Sign users into your own app

Let people sign in to an approved companion app using their Kinabase account.

Feed in telemetry and payments data

Send telemetry readings to Kinabase and work with payment records synced from GoCardless.

---

2. Before you start

The Kinabase API is enabled per organisation. If you can’t see API under Settings → System, contact our support team to enable it for your organisation.

You’ll need to sign in as a System admin to create and manage App Registrations. Ask the developer or integration provider what they need before creating one.

---

3. Register an app

Each integration needs its own App Registration. Keeping registrations separate lets you identify, disable, or remove one integration without affecting the others.

1. Open the API pane

Click your name in the bottom-left corner of Kinabase, select Settings, open the System section, and select API.

2. Add an app registration

Click Add, then give it a Name and a Description so your team knows what it’s for.

3. Decide whether it needs to sign users in

Leave Allow this app to sign in users off unless the developer or integration provider tells you that people need to sign in through the integration. If you turn it on, enter the Display name and Redirect URIs they provide. Leave Allowed scopes and Require client secret on token exchange at their defaults unless the developer documentation gives you different instructions.

4. Create the registration and copy its credentials

Click Add to create the registration. Kinabase shows its App Id and App Secret once in the App registration created dialog.

Copy both credentials to an approved password manager or secret store before clicking Done. Treat the App Secret like a password, and share it only with the developer or provider responsible for the integration, using an approved secure method. The secret cannot be retrieved later. If it is lost, create a new app registration.

---

4. Disable or enable an app registration

Disable an app registration when a connected system needs to stop signing in or calling the API. Kinabase keeps its App Id, App Secret, and user sign-in configuration, so you can enable it again without rebuilding the registration.

Disable a registration

1. Find the registration under Settings → System → API and open its Actions menu.
2. Select Disable.
3. Review the warning, then click Disable to confirm.

The change takes effect immediately. The app cannot request new API tokens, use existing tokens, or sign users in. A Disabled badge and the message This app cannot sign in or call the API until it is enabled. identify the registration in the list.

Enable a registration

1. Open the disabled registration’s Actions menu.
2. Select Enable.
3. Review the message, then click Enable to confirm.

The connected system can sign in and call the API again using the registration’s existing credentials and configuration.

If an App Secret is exposed or lost, keep the registration disabled and create a replacement. Kinabase cannot retrieve or change an existing secret.

---

5. Explore the interactive documentation

Every App Registration pane includes an Open API documentation link. This opens technical documentation for your organisation and should be used by the person building the integration.

For authentication instructions, data formats, available operations, and usage limits, see our developer documentation.

---

6. Send data out with the Make an API call step

Inside an Automation

, the Make an API call step can send information from Kinabase to another system — and read what that system sends back, so later steps can use it. You configure it yourself using the other service’s API documentation, which supplies the endpoint, the authentication headers, the request format, and an example response.

Because this step can share record data outside Kinabase, ask someone familiar with the receiving system to help configure and test it.

This step sends information out of Kinabase. An event in another system cannot currently start a Kinabase automation, and the step cannot be used to call the Kinabase API itself.

For step-by-step configuration — methods, URLs, headers, request bodies, and capturing the response — see Making an API Call. For the full step catalogue, see Automation steps.

The Make an API call step is available on the Max plan.

---

To get started, agree the requirements with your developer or integration provider, then register the integration under Settings → System → API.

---

Need more help? Ask your System admin, or contact our support team via Help & Support.