Create access for a specific purpose
Give each connection a clear job, such as reading reporting data or supporting an internal workflow. Review the account access it actually needs.
Use account API keys to connect your own software with supported Lead Source data and actions.
Connections · Built for US call workflowsChoose the account information or supported action your own software needs.
Create and manage the appropriate account API key.
Verify the result and the handling of failures before depending on the connection.
Explore the steps above. Sample details show the workflow, not a live account.
Connections
Your call operation may need to work with tools your team already uses. API access gives developers a controlled way to build those connections around supported account operations.
Give each connection a clear job, such as reading reporting data or supporting an internal workflow. Review the account access it actually needs.
Manage API keys and revoke access when a connection is retired or a key should no longer be used. Treat keys as credentials, not information to share in public.
Decide which records need to move, which system owns the next step, and how the team will review failures. An API is a building block for a connection, not a ready-made integration with every tool.
From setup to review
Choose the account information or supported action your own software needs.
Create and manage the appropriate account API key.
Verify the result and the handling of failures before depending on the connection.
A closer look
Explore the workflow above, then bring your own requirements to an early-access conversation.
No. This page explains the purpose of API access. The documentation area will hold the detailed reference and setup material as it becomes available.
No. A custom connection needs implementation and testing. Use the available API capabilities for the operations they support.
Meet your next growth tool
Get an early look at Lead Source, built for the way your business handles calls.