Developer APIs for Agency Integration

Connecting external systems to our products requires a clear understanding of the available methods. For many agencies, website embeds or dedicated plugins provide sufficient functionality. However, for deeper integration into client applications and custom workflows, a direct Application Programming Interface (API) is often necessary. We offer two primary API-led integration patterns: a REST API for request-response interactions, ideal for tasks like data validation, and webhooks for pushing real-time event notifications from our system to yours. This allows your services to react instantly to events, such as a phone call being completed, without constantly polling our servers for updates. Choosing the correct route depends entirely on the client's objective.

Our approach is to provide specific, documented APIs for select products rather than a single, universal API for the entire AutoThink platform. This ensures stability and clear purpose for each interface. It is also important to distinguish these product APIs from emerging standards like the Model Context Protocol (MCP). A product API allows one system to talk to another in a structured way. MCP is an open standard designed to allow AI agents to connect to tools and data sources. While we monitor developments in this area, our focus for general agency integration remains on robust, well-defined REST APIs and webhooks. Discussions around MCP are handled separately for specialist use cases.

AutoPostcode offers a REST API designed for one specific, critical function: validating UK addresses and related data at the point of capture. Agencies can integrate this API into client websites, ecommerce checkouts, and custom-built applications. By calling the API with a partial address or postcode, your client's system receives structured, validated address data in return. This is a common implementation project for web development and automation agencies seeking to improve the quality of customer data entering a client's CRM, order management system, or database. Correctly implemented, it reduces downstream errors, improves delivery accuracy, and supports a cleaner data environment for the client.

For agencies providing marketing analytics and sales intelligence, Call Bullet offers a read-only developer API and a webhook service. The read-only API allows you to programmatically retrieve call data and integrate it into your own internal dashboards, client-facing reports, or business intelligence tools. This enables you to build a consolidated view of marketing performance. The webhooks provide a more immediate, event-driven integration. You can configure a webhook to send a notification to your own application whenever a call starts or finishes, pushing data directly into a client's CRM to log the activity or triggering a follow-up workflow in an external system.

It is important to be clear that most AutoThink products are managed via their dedicated web applications and do not currently have public-facing APIs for general agency use. Products such as AutoEmails, AutoPersonify, and Call Qualitix are delivered as managed services through their respective platforms. We do not offer a single, unified API that provides access to all AutoThink tools, nor do we provide read-write access to the internal databases of these applications. Our strategy is to release APIs only where there is a clear, stable, and secure use case that benefits our agency partners and their clients. We advise against assuming API availability for any product not explicitly mentioned here.

We also need to clarify the status of the Model Context Protocol (MCP). MCP is an open standard designed to help AI agents interact with external tools and data, which is a different function from a conventional product API. As of 2026, AutoThink products do not ship with built-in MCP servers as a standard feature. While we are open to discussing potential MCP integrations for highly specific, experimental AI agent workflows, this is not a generally available option. Such conversations are held on a product-by-product basis with specialist automation agencies and are considered bespoke development projects, separate from our standard API offerings.

Consider an agency managing a multi-channel marketing campaign for a professional services client. The client invests in PPC, social media, and print advertising, but finds it difficult to attribute inbound phone enquiries to the correct source. This makes it hard for the agency to demonstrate the value of specific channels and to optimise the marketing budget effectively. The agency decides to use Call Bullet to solve this attribution problem, but they want to integrate the results directly into the client's existing CRM and their own reporting suite, rather than using another separate dashboard.

The agency implements Call Bullet's dynamic number insertion on the client's landing pages. When a prospect calls a tracked number, a webhook is configured to fire at the end of the call. This webhook sends a JSON payload containing the call's source, duration, and a link to the recording to a small application the agency hosts. This application parses the data, formats it, and then uses the CRM's own API to create a new activity record against the relevant campaign. Simultaneously, it pushes key metrics to the agency's central BI tool. The client gets real-time call attribution in their CRM, and the agency has the data to prove its impact.

Access to our developer APIs is not self-service. The process begins with a conversation to understand your agency, your client, and the specific use case you intend to address. This initial consultation allows us to confirm that the chosen API is a suitable technical solution and to outline the commercial model. Our pricing for API access typically involves a setup fee and an ongoing retainer or a per-client management fee, reflecting the value of the integration. We do not offer a standard reseller programme or commission structure. Our focus is on establishing a direct, supportive commercial relationship with the agencies we work with.

Once a use case is mutually agreed upon, we move to the technical onboarding phase. We will provide your development team with the necessary credentials, such as API keys, and grant them access to the complete technical documentation. This documentation details the available endpoints, data formats, authentication methods, and example code. We also clarify the specific rate limits and usage policies that apply to ensure a stable service. Our objective is to provide a clear, predictable, and robust framework that supports your development process and leads to a successful and sustainable client solution.