The LeadScout API, API keys and webhooks

API keys are for server-to-server integrations.

1. Under API keys, click New key. 2. Give it a name, such as "Sales dashboard sync". 3. Tick the scopes it needs: - prospects:read: read prospects, notes, appointments, status history, statuses and tags. - prospects:write: create, update and delete prospects, notes, appointments and status changes. - users:read: read your team members. - webhooks:manage: create and manage webhook subscriptions. 4. Click Create key and copy the secret. It is shown only once.

Each active key uses a seat, like a team member, and the dialog tells you whether that changes your bill. Changes made with a key show up in LeadScout as "Key name (API)". You can rename a key at any time. Revoke stops it immediately, deletes its webhooks and frees its seat.

If you are building an app that other LeadScout customers connect, register it under OAuth apps with a name and one or more redirect URIs. You get a client ID and a client secret; the secret is shown once and can be rotated later. Owners and admins of any LeadScout organization can then connect your app and approve its scopes.

Connected apps lists the apps people in your organization have authorized, including AI agents. Each one acts as the person who connected it. Click Revoke to disconnect an app for your organization; it loses access right away.

Webhooks are registered through the API by your integration, and listed under Webhooks with their URL, events and status. Events cover prospects (created, updated, deleted and status changed), notes (created) and appointments (created and deleted), whether the change was made on the web, on a phone, by an agent or through the API. Bulk operations such as the CSV import do not send webhooks. Revoking the key or app that owns a webhook deletes it.