Reference

Create a CRM connection

POST /v1/connections. Start a connection to HubSpot, Salesforce, Google Sheets, Deliverite, a webhook or CSV.

Generated from the contractsView as Markdown

POST /v1/connections

Start a connection to HubSpot, Salesforce, Google Sheets, Deliverite, a webhook or CSV. OAuth providers return an authorise_url for a person to approve in the app.

Property	Value
Endpoint	`POST https://mydatahub.emailmovers.com/v1/connections`
Operation id	`createConnection`
Cost	Free (0 credits)
Access	An API key or an OAuth 2.1 token with the scope `pushes:write`.
Idempotency-Key	Optional. Makes a retry safe.
Tag	CRM push

Request

Parameters

Name	In	Type	Required	Description
`MyDataHub-Version`	header	string	no	The dated API version, pinned per key when left out. Non-breaking changes ship as new dates; the path major changes only for breaking changes, with a 12 month deprecation window.
`Idempotency-Key`	header	string	no	Makes the request safe to retry: the same key returns the stored response. Keys are kept for the life of the organisation.

Body

Member	Type	Required	Description
`provider`	enum: `hubspot`, `salesforce`, `google_sheets`, `deliverite`, `webhook`, `csv`	yes
`name`	string	yes
`webhook_url`	string (uri)	no	Provider webhook only, and required there: the https endpoint to post to.

Example request

curl -X POST "https://mydatahub.emailmovers.com/v1/connections" \
  -H "Authorization: Bearer $MYDATAHUB_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
  "provider": "hubspot",
  "name": "Sales HubSpot"
}'

Responses

201: The connection.

Headers: RateLimit, RateLimit-Policy, Location.

Member	Type	Always present	Description
`id`	string	yes	Format: a CRM connection id: conn_ followed by a 26 character ULID in upper case Crockford base32, such as conn_01JB3Y2X6Y7Z8A1B2C3D4E5F6G.
`provider`	enum: `hubspot`, `salesforce`, `google_sheets`, `deliverite`, `webhook`, `csv`	yes
`name`	string	yes
`status`	enum: `pending_authorisation`, `connected`, `expired`, `revoked`	yes
`authorise_url`	string (uri) or null	yes	Where a person authorises the connection in the app, while pending_authorisation.
`read_only_overlap`	boolean	yes	Whether the connection may read email hashes for the New to you overlap check.
`created_at`	string (date-time)	yes
`last_used_at`	string (date-time) or null	yes

Example response

{
  "id": "conn_01JB3Y2X6Y7Z8A1B2C3D4E5F6G",
  "provider": "hubspot",
  "name": "Sales HubSpot",
  "status": "pending_authorisation",
  "authorise_url": "https://mydatahub.emailmovers.com/connections/conn_01JB3Y2X6Y7Z8A1B2C3D4E5F6G/authorise",
  "read_only_overlap": true,
  "created_at": "2026-09-20T09:30:00Z",
  "last_used_at": null
}

Errors

Every error is a problem object with a code and a next_step. Every response carries the RateLimit and RateLimit-Policy headers; see Rate limits.

Status	Problem codes	When
400	`invalid-request`, `idempotency-key-required`, `unsupported-version`	The request could not be read, or an Idempotency-Key is missing.
401	`authentication-required`, `account-required`	Sign in (OAuth) or send an API key (authentication-required), or create a free account for what the anonymous tier does not cover (account-required).
403	`insufficient-scope`, `confirmation-required`, `business-details-required`, `licence-acceptance-required`, `dpa-acceptance-required`, `agent-budget-exceeded`	The token lacks a scope (insufficient-scope, with required_scope and a WWW-Authenticate step-up challenge); no person confirmed the spend and no agent key covers it (confirmation-required, with an approval_url); an agent key's per-order cap or monthly budget does not cover it (agent-budget-exceeded); an account made by self-serve sign-up has not yet confirmed its business name and that it is a UK business, which its first order needs (business-details-required); the order needs the Data Licence and Sharing Agreement accepted at the version in force (licence-acceptance-required); or a suppression upload comes before the organisation has accepted the Article 28 data processing agreement in force (dpa-acceptance-required). Nothing is charged.
409	`idempotency-key-reused`, `quote-expired`, `order-not-ready`, `order-not-cancellable`	An Idempotency-Key reused with different parameters, an expired machine quote, or an object in the wrong state.
422	`validation-failed`, `quote-required`, `dataset-unavailable`	The request is not valid. errors lists every problem with a JSON pointer and did_you_mean.
429	`rate-limited`	Too many requests. Wait for Retry-After.
Any other failure	`internal-error`, `service-unavailable`, `tps-screen-expired`	Something failed on our side (500 internal-error) or the service is briefly unavailable (503 service-unavailable, with Retry-After). Nothing was charged; retry with the same Idempotency-Key. A count, sample, quote or order with telephone in play is also refused with 503 tps-screen-expired, with no Retry-After, while the dataset version's TPS and CTPS screen is more than 28 days old.