Developers

Build on Toolbase

Connect internal systems, websites and AI assistants to Toolbase through authenticated APIs. Every request runs with the permissions of the key or user behind it.

Request API accessView integrations
Illustrative request. Endpoints and fields are confirmed in the developer documentation.
curl https://app.toolbase.com.au/api/v1/leads \
  -H "Authorization: Bearer $TOOLBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "firstName": "Jordan",
    "lastName": "Example",
    "email": "jordan@example.com",
    "source": "Website"
  }'

Capabilities

Three ways to connect

REST API Beta

Read and write Toolbase records such as leads, contacts, deals and quotes over HTTPS with JSON.

Webhooks Coming Soon

Planned: receive a signed HTTP request when records change. Inbound lead capture from web forms is available today.

MCP Beta

Let AI assistants such as Claude use Toolbase tools under a user's own permissions, with audit logging.

Architecture

How integration works

  • API keys

    Keys are created by an administrator inside Toolbase, scoped to a tenant and revocable at any time. Keep them server-side.

  • Authentication

    Requests are authenticated with a bearer token. MCP connections use an authorisation flow tied to a Toolbase user.

  • Integration architecture

    Integrations call the Toolbase API. Nothing connects to the database directly, including this website.

  • Rate limits

    Requests are rate limited per key to protect the platform. Limits are published in the developer documentation.

  • Developer documentation

    Reference documentation is provided with API access while the API is in beta.

  • Sandbox

    A sandbox tenant with demo data can be arranged for building and testing integrations.

Building an integration?

Tell us what you want to connect and we will arrange access.

Request API accessBook a Demo