Email marketing
Kit in your product and your AI agents, through one API
The Kit toolkit covers subscribers, tags, forms, segments, broadcasts with their stats, and growth stats: list, create, update and apply. Customers connect Kit once with OAuth on your own app, and Connect renews the tokens and logs every execution, so your product or AI agent runs email marketing without a custom integration.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/kit_create_subscriber/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"email_address": "<email_address>"
}
}How it works
From a connected customer to the first Kit call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Kit 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 Kit.
Add signups to the list
When someone signs up in your product, create the subscriber and apply a tag, which also starts the automations of the account that begin with that tag.
Draft and schedule broadcasts
Create a broadcast as a draft, target segments and tags with subscriber_filter, and schedule it with send_at once the user approves.
Reports on audience growth
Pull List broadcast stats and Get growth stats into a dashboard for your agency clients: opens, clicks, new subscribers and cancellations.
Tools
13 Kit tools
- List subscribersGETLists the subscribers with their id, email, first name, state and custom fields, only the active ones by default. Look one up by email_address. The response has subscribers and pagination; while has_next_page is true, pass pagination.end_cursor as after.
- Create subscriberPOSTCreates an active subscriber. When the email address already belongs to a subscriber, it updates the first name of that subscriber instead. It adds no tag: use Apply tag next.
- Update subscriberPUTUpdates the email address, first name or custom fields of a subscriber. A custom field key that does not exist in the account makes the request fail.
- List tagsGETLists the tags with their id, name and creation date. The response has tags and pagination; while has_next_page is true, pass pagination.end_cursor as after.
- Create tagPOSTCreates a tag and returns it with its id. When a tag with the same name exists, ignoring case, it returns that tag instead of a duplicate.
- Apply tagPOSTApplies a tag to an existing subscriber, found by email address. Automations of the account that start with this tag run for the subscriber. Create the subscriber first with Create subscriber.
- List formsGETLists the forms and landing pages with their id, name, type and embed URL, only the active ones by default. The response has forms and pagination; while has_next_page is true, pass pagination.end_cursor as after.
- List segmentsGETLists the segments with their id and name. Segments are built in the Kit app, and their ids target a broadcast in subscriber_filter. The response has segments and pagination; while has_next_page is true, pass pagination.end_cursor as after.
- List broadcastsGETLists the broadcasts with their id, subject, content, status, send_at, targeting and email template. The response has broadcasts and pagination; while has_next_page is true, pass pagination.end_cursor as after.
- Create broadcastPOSTCreates a broadcast email as a draft, or schedules it when send_at is set. It goes to every subscriber, or only to the segments and tags in subscriber_filter. Returns the broadcast with its id.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/kit, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
Questions about the Kit toolkit
Do I need to build against the Kit API?
No. Connect ships 13 Kit 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 Kit account?
With the mode the toolkit accepts: OAuth with your product's app. 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.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
