Engage

Automation and data

Public REST API + Purple Engage

Connect a system that has no ready-made connector, with your own developers in control.

What syncs, and which way

Both ways between Public REST API and Engage

A documented public API with 39 paths and 19 scopes lets your systems read and write contacts, tags, events and consent.

  • Contacts, tags, events and consent, read and written
  • 39 paths, including segments, automations, campaigns and reports
  • 19 scopes, and up to 600 requests a minute per key
  • Bulk jobs of up to 1,000 contacts
Explore customer data in Engage

Put the connection to work

Two ways to use Public REST API with your Engage marketing.

Add customer context

Create and read contacts, tags and events from your own systems.

Keep consent connected

Read and write consent as part of the integration you build.

How to set up Public REST API

  1. Make a scoped API key with only the scopes your integration needs.

  2. Have your developers call the documented paths, within 600 requests a minute per key.

  3. Use bulk jobs of up to 1,000 contacts for larger loads.

Questions

What connects between Public REST API and Engage?

A documented public API with 39 paths and 19 scopes lets your systems read and write contacts, tags, events and consent.

How do I set up the Public REST API connection?

Make a scoped API key with only the scopes your integration needs. Have your developers call the documented paths, within 600 requests a minute per key. Use bulk jobs of up to 1,000 contacts for larger loads.

What do venues use Public REST API with Engage for?

Connect a system that has no ready-made connector, with your own developers in control.

Put this connection on one guest record

Bring your tools into one marketing platform and approve what your AI team stages.

Talk to the Purple Engage team