Skip to content
Thorbis
Back to roadmap

Platform Quality

Developer API and webhooks

ShippedGenerally available

API keys and webhooks for custom integrations.

Overview

Owners and admins can issue API keys and configure outbound webhooks for their own automations. Settings are role-gated and stay separate from day-to-day field workflows.

What we're building

Every shop runs a few tools Thorbis does not own, and copying data between them by hand does not scale. Without a way to connect, your data stays stuck inside one system.

Thorbis lets owners and admins issue API keys and configure outbound webhooks to drive their own automations and integrations. These settings are role-gated to the people who should have them and kept separate from the day-to-day field workflows, so technicians are not exposed to developer controls.

It is for owners, admins, and the developers they work with who want to wire Thorbis into their own stack.

What you'll be able to do

  • Issue API keys
  • Configure outbound webhooks
  • Build your own automations
  • Connect Thorbis to outside tools
  • Keep developer settings role-gated
  • Separate integration controls from field workflows

Rollout plan

  1. 01

    API key access

    Complete

    Let owners and admins issue API keys for integrations.

  2. 02

    Outbound webhooks

    Complete

    Configure webhooks to push events into custom automations.

  3. 03

    Role-gated controls

    Complete

    Keep developer settings restricted and separate from field workflows.

Milestones

  • Complete:

    API keys

    Add API key issuance.

  • Complete:

    Webhook configuration

    Support outbound webhook setup.

  • Complete:

    Role gating

    Restrict access to owners and admins.

  • Complete:

    Workflow separation

    Keep developer tools out of field workflows.

More in Platform Quality

How to send useful feedback

Name the blocked role

Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.

Explain the workaround

Describe what your team does today and where the process fails under real work.

Define success

Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.

Built for operators

A shared operating layer behind every page

Whether a buyer starts on an industry, feature, migration, or tool page, Thorbis routes the conversation back to the same product system: jobs, money, customers, and team work in one place.

01

One workspace

CRM, dispatch, estimates, invoices, payments, and reporting stay connected.

02

Unlimited users

Bring owners, office staff, dispatchers, techs, and managers into the same system.

03

Guided switch

Migration planning, validation, and cutover support are built into the buying path.