Send event with the Omnisend API
Sends a customer event, creating or updating the contact, and starts the automations of the brand that listen to the event name. Custom events take any name and properties; recommended events, such as placed order, follow the schema of their page in the Omnisend docs.
- Identifier
- omnisend_send_event
The request
POST https://connect.reportei.com/api/tools/omnisend_send_event/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"eventName": "<eventName>",
"origin": "<origin>",
"contact": {}
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| eventName | string | Yes | Name of the event, for example webinar registered, or the name of a recommended event such as placed order. |
| origin | string | Yes | Source of the event: api for a custom store, or the name of the app that sends it. |
| contact | object | Yes | Who the event belongs to, found by email, phone or id. The other fields update the contact. |
| properties | object | No | Properties of the event, keyed by name. Automations and segments can use them. |
| eventVersion | string | No | Only for recommended events: the version given on the page of the event in the Omnisend docs. Leave it out for custom events. |
| eventTime | string | No | When the event happened, as RFC 3339. The default is now. |
| eventID | string | No | Your own UUID for the event. With eventTime, it avoids processing the same past event twice. |
Supported connections
Your customer connects their Omnisend account once, with one of the modes below. The same connection serves every tool of the toolkit.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/omnisend_send_event. It becomes your agent's tool definition with no conversion.
Other Omnisend tools
- List contactsGETLists the contacts with their id, email, phone, status, tags, segments and custom properties, newest first by default. The response has contacts and paging; while paging.hasMore is true, pass paging.cursors.after as after and keep the filters.
- Create contactPOSTCreates a contact, or updates the contact that already has the same email identifier. Setting a channel to subscribed sends the welcome message of the brand, when that automation is on, unless sendWelcomeMessage is false.
- Update contactPATCHUpdates a contact. Only the fields sent change, but tags replaces the whole list of tags: to only add tags, use Apply tags. A channel status in identifiers subscribes or unsubscribes the contact.
- Apply tagsPOSTAdds tags to contacts, keeping the tags they already have. Pick the contacts by contactIDs, emails, phones or segmentID; the selections add up. Limited to 60 calls per minute.
- List segmentsGETLists the segments with their segmentID, name and status. The segmentID targets campaigns and filters contacts. The response has segments and paging; while paging.hasMore is true, pass paging.cursors.after as after.
- List email templatesGETLists the email templates with their id and name, newest first by default. The id is the body of an email campaign. The response has templates and paging; while paging.hasMore is true, pass paging.cursors.after as after.
- List campaignsGETLists the campaigns with their id, name, status, channel, content, audience and sending settings, newest first by default. The response has campaigns and paging; while paging.hasMore is true, pass paging.cursors.after as after and keep the filters.
- Create campaignPOSTCreates a regular email or SMS campaign as a draft and returns it with its id. An email campaign needs content.email.templateID, from List email templates, and an SMS campaign needs content.sms. Nothing is sent until Send campaign.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
