Who this is for
Technical admins and operators connecting external systems to TruAgents, and partner engineers integrating with the public API.Real integration surfaces
- Public API integration. Programmatic access via the Unsubscribe API and the first-party Python SDK, authenticated with OAuth 2.0 — see Authentication. This is the path for partners who need to sync unsubscribe state from an external service.
- Contact data import. In-app under Contacts → Data Sources. Multiple import paths are supported. The operational guide is on Import and sync data sources.
- Channel infrastructure. Email and SMS delivery readiness is configured in-app under Settings. Start with Connect email and SMS.
Choose your path
- Building an external service that reads or writes TruAgents data? Start with Authentication, then the Unsubscribe API — the Python SDK handles the boilerplate.
- Uploading a contact list to get started? Go to Import and sync data sources.
- Trying to send but blocked because email or SMS isn’t configured? Start with Connect email and SMS.
Common misunderstandings
- Importing data once is not the same thing as setting up an ongoing sync. Verify whether your source keeps delivering updates.
- Channel setup is an integration concern even when it does not feel like one — an unverified sending domain (SPF or DKIM) blocks every campaign just as effectively as a missing contact list.
- An integration being connected does not guarantee the imported data is operationally usable. Check field mappings, dedupe rules, and segment definitions before you rely on the audience.