Skip to main content
Need assistance integrating Extrovert with tools you use? Reach out to support@goextrovert.com

​
Authentication

All API requests require authentication using an API key. Include your API key in the request header: 
x-api-key: YOUR_API_KEY
Using the API requires a plan that includes API access. Requests authenticated with a key on a plan without this capability return 403.

​
Base URL

All API requests should be made to: 
https://api.goextrovert.com/client/v2
The earlier v1 endpoints remain available for backward compatibility at https://api.goextrovert.com/client/v1, but new integrations should use v2.

​
Available Endpoints

The Extrovert API lets you manage your full workspace — campaigns, prospects, and the content that powers engagement. Endpoints are grouped by resource:
  • Campaigns — list, read, create, update, delete, start/stop, duplicate, share, and transfer campaigns (both Prospects and Topic campaigns).
  • Prospects — list and search prospects, look one up by LinkedIn URL, and add new prospects by submitting LinkedIn profile URLs to a prospect list (create a new list seeded with URLs, or add to an existing one). Prospects live in prospect lists, which power Prospects campaigns; you can also move, mark important, and remove them.
  • Topic Bindings — list the Monitored Topics bound to a Topic campaign and replace the full set in one call.
  • Monitored Topics — list, create, update, and delete the AI topics used for post discovery and filtering.
  • Styles — list, read, create, update, duplicate, and delete writing styles, including their comment examples.
  • Contexts — list, read, create, update, duplicate, and delete contexts, including their insights and DM playbooks.
  • Insights & DM Playbooks — manage the insights and DM playbook entries attached to a context.
  • Comment Examples — manage the example comments attached to a style.
  • Workspace & User — read the current plan’s features and quotas, and list your team members.
See the endpoint reference in the sidebar for the full request/response schema of each operation, and try them live in the playground.

​
Response Format

All API responses follow the same JSON envelope: 
{
  "status": "success" | "error",
  "data": null | object | array,
  "message": "Response message",
  "statusCode": 200 | 201 | 400 | 401 | 403 | 404
}
The shape of data depends on the endpoint: a single object for reads, an array for list endpoints, or null for actions that return no payload. On errors, data is null and message describes the problem.

​
Error Handling

The API uses standard HTTP response codes:
  • 200 - OK (successful reads and action endpoints)
  • 201 - Created (a new resource was created)
  • 400 - Bad Request (validation errors, business logic errors)
  • 401 - Unauthorized (invalid or missing API key)
  • 403 - Forbidden (your plan does not include the feature, a quota cap was reached, or you lack access to the resource)
  • 404 - Not Found (the requested resource does not exist or is not visible to you)

​
Getting Started

  1. Obtain your API key from the dashboard
  2. Use the API playground to test endpoints
  3. Integrate the API into your application