Email marketing
Omnisend in your product and your AI agents, through one API
The Omnisend toolkit covers contacts, tags, segments, email templates, campaigns, customer events, reports and products: create and update contacts, apply tags, build and send email or SMS campaigns, send events that start automations, and read aggregated metrics. The customer connects with an Omnisend API key, and your product or AI agent calls every operation through one Connect endpoint.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/omnisend_create_contact/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"identifiers": []
}
}How it works
From a connected customer to the first Omnisend call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Omnisend account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Omnisend.
Sync shoppers into Omnisend
Create or update a contact when a customer signs up or buys in your store, set its channel status and apply tags to feed segments.
Trigger automations from your app
Send a customer event, such as a placed order or a custom event, to start the automations that listen to that event name.
Campaigns and reports by an agent
Let an agent create a draft campaign from a template, send a test email, send it, and later read the report of sends, opens and clicks.
Tools
14 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.
- Update campaignPATCHUpdates a campaign in draft status. Only the fields sent change. The email template stays the one set at creation. To change a campaign that is no longer a draft, the app asks for a copy.
- Send campaign test emailPOSTEmails a preview of an email campaign in draft to up to 5 addresses, with the saved subject, sender and content. The campaign itself does not change.
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.
Questions about the Omnisend toolkit
Do I need to build against the Omnisend API?
No. Connect ships 14 Omnisend tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Omnisend account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
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.
