Webhooks
Webhooks allow Trimoji to send real-time notifications to your application as soon as an event occurs (test completion, campaign creation, etc.). This is the most efficient method for synchronizing your data without unnecessary API calls.
How it works: When an event occurs, Trimoji makes an HTTP POST request to a URL you have configured, attaching the corresponding data.
Step 1
Webhook Configuration
Webhook management is done in your client interface: My Trimoji Account.
Configuration Steps:
-
Enter your server's destination URL (e.g.,
https://your-site.com/api/webhook). - Select the events you wish to listen to.
- Confirm the addition.
- Important: Once the webhook is created, Trimoji automatically generates a unique Secret (Token). You must retrieve this token to secure your endpoint.
Step 2
Security and Authentication
For each transmission, Trimoji uses the generated secret to sign and authenticate the request. You must verify this information on your server to ensure the call originates from our services.
The token is transmitted in two ways with each call:
-
In the HTTP header:
Authorization: YOUR_GENERATED_TOKEN -
In the JSON body:
{ "_token": "YOUR_GENERATED_TOKEN", ... }
Step 3
Payload Structure
All requests sent by Trimoji follow a standardized JSON format for quick action identification.
{ "_token": "trimoji_generated_token", "_timestamp": "2026-02-11T16:00:00.000Z", "_event": "QUIZZ_COMPLETED", // Dynamic data based on the event "id": 12345, "data": { ... } }
Step 4
List of Available Events
You can subscribe to various types of actions based on your automation needs:
-
QUIZZ_SENT -
QUIZZ_COMPLETED
-
PROFILE_UPDATED -
PROFILE_DELETED -
PROFILE_RESTORED
-
CAMPAIGN_CREATED/UPDATED -
PERSONI_CREATED
-
AUTH_LOGIN -
TRANSFER_INCOMING
Step 5
Technical Specifications
-
User-Agent: Requests are sent with the identifier
trimoji/1.0.0. -
Expected Response: Your server should return a
200 OKstatus code. In case of an error on your end, Trimoji logs the failure in your account logs. -
Format: The request body is always in
JSON.