Authenticate requests from 97Display to Email API using an API key with the required scope. Store credentials securely and rotate keys regularly.
97Display authenticates to Email API with the API key in headers. Use TLS and apply least-privilege scopes (users.write).
Primary endpoints: POST /users/ (create), DELETE /users/:userId (remove), PUT /users/:userId (update), GET /workflows/ (read workflows), POST courses/courses-exporter/public/import (import courses). Additional endpoints can be added as needed.
Trigger: when a new contact is added in 97Display, create a corresponding user in Email API.
Actions: POST /users/ with payload including email, name, and initial status.
POST /users/
email, name, status, userId (as returned).
Trigger: updates in 97Display reflect in Email API.
Actions: PUT /users/:userId to sync name, email, and status.
PUT /users/:userId
userId, email, name, status
Trigger: delete in 97Display triggers DELETE /users/:userId
Actions: DELETE /users/:userId in Email API
DELETE /users/:userId
userId
Automated user provisioning between Email API and 97Display.
Real-time data synchronization without manual imports.
Faster campaign setup with consistent contact data.
Key terms, elements, and processes you’ll encounter when building this integration.
A set of definitions and rules that allow apps to talk to each other and exchange data.
How your system proves identity to another system to securely access endpoints.
A specific URL path that performs an action or returns data.
A route that receives real-time data updates from another service.
Automatically create or update users in Email API as new contacts are added in 97Display.
Trigger email campaigns in Email API when a user reaches a milestone in 97Display.
Consolidate analytics from Email API and 97Display for a single dashboard.
Log into Email API, generate or locate your API key, and store it securely.
Enter the Email API base URL and key in 97Display’s integration settings.
Send a test request and verify a successful response.
You don’t need to code. This guide uses no-code connectors and standard API calls to set up the link between Email API and 97Display. You can configure triggers and actions in the UI. If you do prefer code, RESTful calls are straightforward.
Data shared includes contact email, name, status, and identifiers. You can limit fields via API scopes.
All data is transmitted over TLS and API keys are rotated. Use least privilege scopes.
Yes. You can chain multiple actions; ensure rate limits are respected and use batch endpoints where available.
Revoke tokens, rotate keys, and update permissions. Start with a fresh API key and reauthorize connections.
During sync, changes propagate according to configured triggers. You can set up bi-directional syncing if supported.
View logs in Email API and 97Display dashboards or export logs to CSV for audits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
