Skip to main content
The Inflection Developer API gives you programmatic access to the core objects of your workspace. It’s organized around these resources:
  • Contacts: look people up by id or email, create them, and keep their attributes in sync.
  • Contact activity: a contact’s product events, marketing engagement, a change log of record properties, and the mapped Salesforce record.
  • Lists & members: list your static and dynamic lists, and manage static lists and the contacts on them.
  • Emails: create HTML emails in Inflection, list emails, and fetch emails (both HTML and visual editor) by ID.
  • Journeys: list journeys and read a journey’s schedule and derived status.
  • Stats: send and engagement metrics for journeys and emails, with rollups across many journeys or emails in one call.
  • Product users: the product logins underneath a contact, by id or email, with async create and update.
  • Organizations: company accounts, their product users, and a contact’s memberships.
  • Email versions: push per-contact versions of a Personalized Email Asset via POST /v1/email-versions for 1:1 sends at scale. See Send Personalized Emails from Clay for a worked example.
Every path lives under /v2 on the API gateway: https://api.inflection.io. /v2 is /v1 plus more: every /v1 endpoint is served under /v2 unchanged, and /v1 remains published, so existing clients keep working. Journeys, stats, the email and list collections, product users, and organizations are /v2 only. The one exception is POST /v1/email-versions, which is served under /v1.
The API is JSON over HTTPS, authenticated with a bearer token, either a Personal Access Token or an OAuth access token (see Authentication). Reads are synchronous; contact writes are processed asynchronously and return a transaction you poll (see Asynchronous writes).

Quickstart

From zero to your first response in two calls.

Authentication

Tokens, scopes, and what 401 vs 403 mean.