# Omnisend MCP connector The Omnisend connector lets Claude, ChatGPT, Cursor, or any MCP client read and update your Omnisend contacts, tags, products, categories, and campaigns, with each person signed in as themselves and every change recorded in an audit log. Source: https://elaichi.ai/connectors/omnisend/ ## Facts | | | | --- | --- | | Application | Omnisend | | Category | Marketing Automation | | AI tools | 82 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. 82 tools is past the 30-tool threshold, so clients use `search_tools` and `execute_tool` | ## What you can ask once Omnisend is connected - How many Omnisend contacts were created in the last 14 days? - Add the VIP tag to these Omnisend contacts. - List Omnisend products updated this week. ## Connect Omnisend in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Omnisend. 2. Optionally set Share with, then press Connect. 3. Paste an Omnisend API key. One person generates a token in Omnisend and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Omnisend tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Omnisend to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Omnisend to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Omnisend to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Omnisend to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Omnisend tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Omnisend through Elaichi ### Draft the next campaign from a request Marketing. Describe the promotion in plain words and have the agent set up the campaign in Omnisend, ready for you to review before anything is sent. ### Tag a segment before a send Marketing. Ask for every contact who matches a description to be tagged in one go, so the audience is ready in Omnisend when the campaign is. ### Catch a contact up after a conversation Support. After a chat or a phone call, have the agent update the contact record in Omnisend and add or remove the tags that reflect what happened. ### Keep the product catalog current Ecommerce. Add new products, fix prices and descriptions, and tidy product categories in Omnisend without leaving the conversation. ### Load a spreadsheet of subscribers in one batch Operations. Hand over a list of new contacts and have them created in Omnisend as a single batch, then check on the batch to confirm it finished. ### See what went out this month Leadership. Ask which campaigns were sent from Omnisend recently and how the contact list has grown, and get a plain answer pulled from live records. ## Frequently asked questions ### How do I connect Omnisend to Claude? First connect Omnisend in Elaichi by pasting the API key from your Omnisend account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when prompted and Omnisend is available in your conversation. ### Does Omnisend work with ChatGPT and Cursor as well as Claude? Yes. Once Omnisend is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Omnisend once and every client picks it up. ### What can an AI agent actually do with my Omnisend data? It can look up and update contacts in Omnisend, add or remove tags, update many contacts at once, load new contacts as a batch, add and edit products and product categories, and list or set up campaigns. Because Omnisend has a lot of actions available, short concrete asks work best, such as "tag everyone from the Boston store as VIP" rather than a long paragraph. ### Does connecting Omnisend give the AI everything in my account? No. The agent works inside the access of the Omnisend account whose API key was used, and in Elaichi each person signs in as themselves, so every action is tied to a named person. Elaichi can narrow what the AI is allowed to do with Omnisend, for example read-only or contacts only, but it can never widen access beyond what the account already has. ### Can my team share one Omnisend connection? Yes. One person connects Omnisend in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names who updated a contact or created a campaign in Omnisend. ### Can I stop an agent from deleting or changing things in Omnisend? Yes. Restrictions in Elaichi apply per action, so you can allow reading Omnisend contacts and campaigns while blocking deletes or updates to products and categories. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it. ### What happens to an Omnisend connection when someone leaves? Offboarding that person in Elaichi ends their access to Omnisend through every client at once. If they set up a shared Omnisend connection, it keeps working for everyone else on the team. Disconnecting Omnisend once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time. ## All 82 Omnisend tools Every tool below is callable through https://api.elaichi.ai/mcp once Omnisend is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Omnisend contacts** (List). List Omnisend contacts with optional filters by email, phone, status, segment, tag, or update date. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. tag and status are mutually exclusive. - **Create a Omnisend contact** (Create). Create a new Omnisend contact, or update an existing one if the email identifier already matches. Returns: id, createdAt, updatedAt, name, conditionGroups. - **Get single Omnisend contact by ID** (Get). Get a single Omnisend contact by id. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. Required: id. - **Update a Omnisend contact by ID** (Update). Update an Omnisend contact by id. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. Required: id. - **Omnisend contacts add tags** (Add). Batch add tags to Omnisend contacts by contact IDs, emails, phone numbers, or segment. Tagging is asynchronous so tags may not appear immediately. Returns an empty 202 response on success. Required: tags. At least one of contactIDs, emails, phones, or segmentID must also be provided. - **Omnisend contacts delete tags** (Delete). Batch remove tags from Omnisend contacts by contact IDs, emails, phone numbers, or segment. Untagging is asynchronous so tags may not disappear immediately. Returns an empty 202 response on success. Required: tags. At least one of contactIDs, emails, phones, or segmentID must also be provided. - **Omnisend contacts bulk update** (Update). Update an Omnisend contact by email address. Returns: id, createdAt, updatedAt, source, ip, userAgent. Required: email. - **Omnisend brands get current** (Get). Get information about the current Omnisend brand. Returns: brandID, connected, currency, name, platform, timezone, version, website, openapi, info, paths, servers, components. - **Omnisend brands connect current** (Action). Connect your e-commerce store to Omnisend. Returns: brandID, connected, currency, name, platform, timezone, version, website, openapi, info, paths, servers, components. Required: platform, version, website. Only possible via the OAuth flow. - **List all Omnisend products** (List). List products in your Omnisend store catalog. Returns: categoryIDs, createdAt, currency, defaultImageUrl, description, id, images, status, tags, title, type, updatedAt, url, variants, vendor. Results can be sorted by date, updatedAt, or createdAt. - **Create a Omnisend product** (Create). Create a new product in your Omnisend store catalog. Returns the created product id. Required: id, title, url, currency, status. Max 500 variants per product. - **Get single Omnisend product by ID** (Get). Get a single product from your Omnisend store catalog by id. Returns the full product object including id, title, url, currency, status, description, images, variants, categoryIDs, tags, vendor, createdAt, and updatedAt. - **Update a Omnisend product by ID** (Update). Replace a product in your Omnisend store catalog by id with a full product object. Returns the replaced product id. Required: id, title, url, currency, status. - **Delete a Omnisend product by ID** (Delete). Delete a product from your Omnisend store catalog by id. Returns an empty 204 response on success. - **List all Omnisend product categories** (List). List Omnisend product categories, optionally sorted by title, creation, or update date. Returns: categoryID, createdAt, title, updatedAt. Max 250 per page. - **Create a Omnisend product category** (Create). Create a new product category in Omnisend. Returns: categoryID. Required: categoryID, title. - **Get single Omnisend product category by ID** (Get). Get a single Omnisend product category by id. Returns: categoryID, createdAt, title, updatedAt. Required: id. - **Update a Omnisend product category by ID** (Update). Update a product category's title in Omnisend by id. Returns: categoryID. Required: id, title. - **Delete a Omnisend product category by ID** (Delete). Delete a product category in Omnisend by id. Returns an empty 204 response on success. Required: id. - **List all Omnisend batches** (List). List Omnisend batches filtered by endpoint type. Returns each batch with batchID, status, endpoint, method, totalCount, finishedCount, errorsCount, and timestamps. Required: endpoint. - **Create a Omnisend batch** (Create). Create a new batch in Omnisend to asynchronously create or update up to 100 items in a single request. Returns: batchID, totalCount. Required: endpoint, items, method. - **Get single Omnisend batch by ID** (Get). Get a single Omnisend batch by id. Returns the full batch object including batchID, status, endpoint, method, totalCount, finishedCount, errorsCount, and timestamps. Required: id. - **List all Omnisend campaigns** (List). List Omnisend campaigns with filtering by status, channel, type, name, and date ranges, plus sorting. Returns: id, brandID, channel, content, createdAt, endedAt, language, name, sendingSettings, startedAt, status, type, updatedAt, abTest, boosterSettings. - **Create a Omnisend campaign** (Create). Create a new campaign draft in Omnisend supporting regular, abTest, and booster types. Returns the created campaign including id, name, channel, type, status, language, brandID, audience, content, sendingSettings, createdAt, and updatedAt. Required: channel, type. For boosters, boosterSettings.campaignID and boosterSettings.sendTo are also required and each parent campaign supports at most one… - **Get single Omnisend campaign by ID** (Get). Get a single Omnisend campaign by id. Returns the full campaign object including id, name, channel, type, status, audience, content, sendingSettings, createdAt, and updatedAt. Required: id (24-character hexadecimal). - **Update a Omnisend campaign by ID** (Update). Update an Omnisend campaign draft by id. Only campaigns in draft status can be modified; any other status returns 409. Returns the updated campaign including id, name, status, channel, type, content, and sendingSettings. Required: id. - **Delete a Omnisend campaign by ID** (Delete). Delete an Omnisend campaign by id. Returns an empty 204 response on success. Required: id. A 409 is returned when the campaign status does not allow deletion. - **Omnisend campaigns cancel** (Cancel). Cancel an Omnisend campaign by campaign_id and mark it as canceled. Only campaigns in scheduled or paused status (all channel types), or started email campaigns, can be canceled; any other state returns 409. Cancellation of started campaigns is best-effort — messages already in flight may still be delivered. Returns an empty 204 response on success. Required: campaign_id. - **Omnisend campaigns copy** (Copy). Create a draft copy of an Omnisend campaign by campaign_id, copying content, audience, and settings from the original. The new campaign gets its own ID and a name prefixed with 'Copy of: '; the original campaign is left unchanged. Returns the created draft campaign object including id, name, type, channel, status, content, audience, sendingSettings, createdAt, and updatedAt. Required: campaign_id. - **Omnisend campaigns send** (Send). Send an Omnisend campaign draft for sending. Only campaigns in 'draft' status can be sent; to send again, copy the campaign and send the copy. Supports email and SMS campaigns with immediate or scheduled sending strategies. Returns an empty 204 response on success. Required: campaign_id. - **Omnisend campaigns ab test resume** (Test). Resume a stopped A/B test in Omnisend, making automatic winner selection eligible to pick the campaign again. Returns an empty 204 response on success. Required: campaign_id. Available only while the campaign is in stopped status. - **Omnisend campaigns ab test stop** (Test). Stop the A/B test winner-selection phase for an Omnisend campaign, halting automatic winner selection until it is resumed. Returns an empty 204 response on success. Required: campaign_id. Available only while the campaign is in started status. - **Omnisend campaigns ab test winner** (Test). Manually select the A/B test winner for an Omnisend campaign, routing the chosen variant into the send pipeline immediately. The campaign must be an A/B parent. Returns an empty 204 response on success. Required: campaign_id, variantID. - **Omnisend campaigns get UTM** (Get). Get UTM tag settings for an Omnisend campaign. Returns: tags, variants, statistics. Exactly one of tags or variants is present. Required: campaign_id. - **Omnisend campaigns send test email** (Send). Send a test email for an Omnisend campaign to up to 5 recipients, rendering the campaign draft for preview. Only email campaigns are supported. Returns an empty 204 response on success. Required: campaign_id, recipients. - **Omnisend campaigns bulk update** (Update). Replace UTM tag settings for an Omnisend campaign. Send a tags object for regular campaigns or a variants object for A/B test campaigns — exactly one must be present. The campaign must be in draft status. Returns: statistics. Required: campaign_id. - **List all Omnisend segments** (List). List Omnisend segments with cursor-based pagination and single-field sorting. Returns: segmentID, name, conditionGroups, status, isStarred, createdAt, updatedAt, archivedAt. Max 50 per page. Sortable by createdAt or name. - **Create a Omnisend segment** (Create). Create a new Omnisend segment with condition-based rules. Returns: name, conditionGroups, createdAt, updatedAt. Required: name, conditionGroups. - **Get single Omnisend segment by ID** (Get). Get a single Omnisend segment by id. Returns: segmentID, name, conditionGroups, status, isStarred, createdAt, updatedAt, archivedAt. Required: id. - **Update a Omnisend segment by ID** (Update). Update an existing Omnisend segment by id. The segment must not be in a building state. Returns: segmentID, name, conditionGroups, status, isStarred, createdAt, updatedAt, archivedAt. Required: id, name, conditionGroups. - **Delete a Omnisend segment by ID** (Delete). Delete an Omnisend segment by id. The segment must not be in a building state or a 409 Conflict error is returned. Returns an empty 204 response on success. Required: id. - **Omnisend segments get statistics** (Get). Get statistics for an Omnisend segment including the total number of matching contacts. Returns: contactsCount. Required: segment_id. - **Get single Omnisend email content by ID** (Get). Get an Omnisend email content object by its ID (same as the template ID returned at template creation). Returns the full content structure including generalSettings (global appearance: logo, body, buttonPresets, textPresets) and sections (top-level containers of rows, columns, and blocks). Required: id. - **Update a Omnisend email content by ID** (Update). Update (fully replace) Omnisend email content by id. Returns the updated content object including its id, generalSettings, and sections. Required: id. The full content structure must be provided — omitted sections are deleted. Request body limit 1 MB; locked content (during or after a campaign send) returns 409. - **Omnisend email content render** (Action). Render Omnisend email content to HTML by ID for preview. Returns: reports. Required: email_content_id. The content is rendered with an empty data context (no contact, no marketing activity). - **List all Omnisend email templates** (List). List Omnisend email templates with cursor-based pagination. Returns: createdAt, id, name, updatedAt. Supports sorting by createdAt or name and filtering by name with nameContains. Max 100 items per page. - **Create a Omnisend email template** (Create). Create a new email template in Omnisend with a hierarchical layout of sections, rows, columns, and blocks. Returns the created template including id, name, createdAt, updatedAt, generalSettings, and sections. Required: name, generalSettings, sections. At least 1 section required; template name 1–255 characters; request body max 1 MB. - **Get single Omnisend email template by ID** (Get). Get a specific Omnisend email template by id, returning the full template object including its id, name, generalSettings, sections, createdAt, and updatedAt. Required: id (24-character hexadecimal). - **Update a Omnisend email template by ID** (Update). Fully replace an Omnisend email template by id. Returns the updated template including its id, name, generalSettings, and sections. Required: id and a complete template body. - **Delete a Omnisend email template by ID** (Delete). Delete an Omnisend email template by id. Returns an empty 204 response on success. Required: id. - **Omnisend email templates import** (Import). Import an Omnisend email template from raw HTML content; the HTML is parsed, styles extracted, and structured into a template. Returns the created template object including id, name, content, createdAt, and updatedAt. Required: name (1–255 characters), html. Request body size limit 1 MB. - **Omnisend email templates render** (Action). Render an Omnisend email template by ID to produce the full HTML body for preview purposes. Returns an object whose property values are rendered content strings. Required: email_template_id. - **List all Omnisend email universal layouts** (List). List Omnisend email universal layouts sorted by creation time (newest first). Returns: id, name, content. Filter by name with nameContains. Max 250 items per page. - **Create a Omnisend email universal layout** (Create). Create a new reusable email universal layout in Omnisend. Returns the created layout object including its id, name, and content with its rows, columns, and blocks. Required: name, content. All element IDs within the layout must be unique 24-character hex strings; request body must not exceed 1 MB. - **Get single Omnisend email universal layout by ID** (Get). Get a single Omnisend email universal layout by id. Returns: id, name, and content (a section containing rows, columns, and blocks). Required: id. - **Update a Omnisend email universal layout by ID** (Update). Update (fully replace) a universal email layout in Omnisend by id. Returns the updated layout object including id, name, and content (with its rows, columns, and blocks). Required: id, name, and content. The full layout structure must be supplied — omitted elements are removed. - **Delete a Omnisend email universal layout by ID** (Delete). Delete an Omnisend email universal layout by id. Returns an empty 204 response on success. Required: id. - **List all Omnisend images** (List). List images for a brand in Omnisend with cursor-based pagination, sorting, and name filtering. Returns: createdAt, height, id, name, size, type, url, width. Max 250 items per page. - **Create a Omnisend image** (Create). Upload an image to Omnisend from a publicly accessible URL. Returns the created image object including id, name, url, type, size, width, height, and createdAt. Required: url. - **Get single Omnisend image by ID** (Get). Get a single image in Omnisend by id. Returns: createdAt, height, id, name, size, type, url, width. Required: id. - **Delete a Omnisend image by ID** (Delete). Delete an image in Omnisend by id. Returns an empty 204 response on success. Required: id. - **Omnisend images upload** (Upload). Upload an image file directly to Omnisend via multipart form data. Returns the created image object including id, name, url, type, size, width, height, and createdAt. Required: file. Supported formats: JPEG, PNG, GIF, WebP, max 5MB. - **Omnisend analytics generate report** (Generate). Generate an Omnisend marketing analytics report with aggregated delivery, engagement, and revenue metrics grouped by message send date. Returns: reports. Required: queries (1–4 per request, each with alias, metrics, and dateRange interval). Rate limited to 10 requests/minute and 55/day per brand. - **Omnisend analytics generate statistics** (Generate). Generate an Omnisend marketing analytics report with aggregated delivery, engagement, revenue, and audience growth metrics grouped by event date. Returns a statistics array where each result entry includes alias, dimensions, metrics, and rows. Required: queries (each requires alias, metrics, dimensions including timestamp, and dateRange from/to). Up to 4 queries per request; rate limited to 10… - **List all Omnisend automations** (List). List automation workflows in Omnisend with filtering by name, enabled state, and created/updated date ranges, plus sorting options. Returns: id, name, isEnabled, createdAt, updatedAt. Max 250 per page, default 100. - **Create a Omnisend automation** (Create). Create a new automation workflow in Omnisend. Returns the created automation including id, name, blocks, trigger, settings, isEnabled, createdAt, and updatedAt. Required: name, trigger, blocks. Automations are created disabled and must be explicitly enabled before processing trigger events. - **Get single Omnisend automation by ID** (Get). Get a single Omnisend automation workflow by id. Returns the full automation object including id, name, blocks, trigger, settings, exitConditions, isEnabled, brandID, createdAt, updatedAt, enabledAt, and disabledAt. Required: id (24-character hexadecimal). - **Update a Omnisend automation by ID** (Update). Update an Omnisend automation workflow by id, changing only the fields provided in the request body. Returns the full automation object including id, name, isEnabled, blocks, trigger, settings, createdAt, and updatedAt. Required: id. Enabled automations cannot be patched — disable the automation first via the disable endpoint, then re-enable it after making changes. - **Delete a Omnisend automation by ID** (Delete). Delete a single Omnisend automation workflow by id. This operation is idempotent — deleting a non-existent automation Returns an empty 204 response on success. Returns an empty 204 response on success. Required: id. - **Omnisend automations copy** (Copy). Copy an Omnisend automation workflow to create a disabled duplicate. Returns: id, createdAt, updatedAt, condition. Required: automation_id. The copy is always created in a disabled state regardless of the source automation's status; an optional name may be provided in the request body. - **Omnisend automations disable** (Disable). Disable an Omnisend automation workflow so it stops accepting new trigger events. Returns the automation object including id, name, isEnabled, createdAt, updatedAt, and disabledAt. Required: automation_id. The body's contactsInWorkflow option (keep or exit) controls in-flight contacts, and the call is idempotent for already-disabled workflows. - **Omnisend automations enable** (Enable). Enable an automation workflow in Omnisend so it starts processing trigger events in real time. Returns the automation object including id, name, isEnabled, enabledAt, and blocks. Required: automation_id. The request body is optional — set enrollExisting to true to also enroll contacts who already qualify at enable time. - **Omnisend automations get UTM** (Get). Get aggregated UTM tracking tags for all send-action blocks in an Omnisend automation. Returns: blocks, condition. Required: automation_id. - **Omnisend automations get block UTM** (Get). Get UTM tracking tags for a specific Omnisend automation send-action block. Returns: tags, condition. Required: automation_id, block_id. Missing or cleared tags are returned with their default values. - **Omnisend automations update block UTM** (Update). Update UTM tracking tags for a specific Omnisend automation send-action block. Returns: tags, logicalOperator, filters. Required: automation_id, block_id, and tags. All three tag fields are replaced atomically; send an empty string to clear a field. - **Omnisend automations send block test email** (Send). Send a test email from a specific Omnisend automation email block to up to 5 recipients. Returns an empty 204 response on success. Required: automation_id, block_id, recipients. The email is rendered and delivered asynchronously. - **Omnisend automations bulk update** (Update). Replace the full block tree for an Omnisend automation workflow. Blocks identified by `id` are updated in place, blocks with `temporaryID` are created, and existing blocks not included are removed. Returns: id, name, blocks, trigger, settings, isEnabled, createdAt, updatedAt. Required: automation_id. Enabled automations cannot be restructured — disable the automation first, then re-enable after… - **Create a Omnisend event** (Create). Send a customer event to Omnisend to track behavior and trigger automations. Supports custom events and predefined recommended events. Returns an empty 202 Accepted response on success. Rate limited to 400 requests per minute. - **Create a Omnisend event metadatum** (Create). Create a new brand-custom event schema in Omnisend, identified by the combination of name and origin. Returns the created event including name, displayName, origins, explicitlyDefined, and the nested property tree. Required: name, origin, displayName, properties. Optional metadata fields must be omitted rather than sent as null. - **Omnisend event metadata query** (Search). Query Omnisend event metadata by category, optionally filtered by event names and origins. Returns a list of events each with name, displayName, origins, explicitlyDefined, and optionally the nested property tree. Required: category. Supported categories: automations, events, segments. Set includeProperties to true to include the property tree. - **Omnisend event metadata bulk update** (Update). Update (merge) an existing brand-custom event schema in Omnisend, identified by name and origin. Only supplied fields are applied; omitted metadata and properties are preserved and no property is deleted. Returns the merged event including name, displayName, origins, explicitlyDefined, and the nested property tree. Required: name, origin. The type of an already explicitly-defined property cannot… - **List all Omnisend batch items** (List). List Omnisend batch items for a given batch, showing individual item results including the original request, response, and processing status. Returns: itemID, request, response, responseCode, status. Required: batch_id.