FieldCamp

API Access | AI Dispatcher

Create a personal API token in AI Dispatcher, send it as a Bearer token, and authorise third-party apps through the OAuth consent screen.

API Access is where you get the credential an external script, integration or AI assistant uses to call AI Dispatcher on your behalf.

Before you begin

  • API Access sits in workspace settings, so you need access to Settings.
  • A token carries your own access. Anyone holding it can do what you can do.

Create a personal API token

  1. Open Settings > API Access.
  2. In Personal API token, create a token.
  3. Copy it immediately and store it in your secrets manager.

Use the token

Send the token as a Bearer token in the Authorization header of every request:

Authorization: Bearer <your-token>

The Using your token panel on the same page shows the exact header format to copy.

Keep tokens out of source control, screenshots and shared documents. If a token is exposed, revoke it on this page and issue a new one — revoking takes effect immediately for every client using it.

Authorising an app instead of pasting a token

Applications that support OAuth send you to AI Dispatcher's consent screen instead of asking for a token. Review what the app is asking for and approve it there; the app receives its own credential and you never copy or store a token.

Where to Review Call Recordings and AI Summaries in FieldCamp

Call recordings, transcripts, and AI summaries in FieldCamp live under the Calls add-on (Inbox and the /calls workspace), not under AI Dispatcher. This page points you to the right docs.

How AI Dispatcher Works | AI Dispatcher

Deep dive into how FieldCamp's AI Dispatcher analyzes hundreds of variables in milliseconds — constraint checking, multi-factor scoring, confidence levels, and continuous learning.

On this page

Before you beginCreate a personal API tokenUse the tokenAuthorising an app instead of pasting a tokenRelated articles