Omnisend

Fetch the connected Omnisend brand (store): brandID, name, currency, platform, timezone and whether the store is connected.

List contacts. Filter by email, phone, subscription status, segment or tag. Two combinations the API rejects are refused locally: tag with status, and updatedAtFrom with email/phone/status/segmentID/tag.

Fetch one contact with its identifiers, channel statuses, tags and custom properties.

Create a contact. At least one identifier (email or phone) is required. An identifier already owned by another contact is ignored by Omnisend, and a contact with no usable identifier is not created.

Update an existing contact's profile fields, identifiers, tags or custom properties. Only the fields you pass change.

Add tags to many contacts at once, selected by contact ids, emails, phone numbers or a segment id.

Remove tags from many contacts at once, selected by contact ids, emails, phone numbers or a segment id.

Send a customer event to trigger automations and feed segmentation. Use a recommended e-commerce event name ("added product to cart", "started checkout", "placed order", "paid for order", "ordered product", "order refunded", "order fulfilled", "order canceled", "viewed product") with its documented eventVersion and properties, or any custom name with eventVersion omitted. Carts and orders are represented as these events — Omnisend has no separate cart or order resource.

List the store's contact segments.

Fetch one segment with its condition groups.

Fetch a segment's membership statistics.

Create a segment from condition groups. Each group holds conditions on contact fields or events; see the vendor's segmentation reference for the condition grammar, and get_segment on an existing segment for a worked example.

List campaigns with their status, channel, type, audience and schedule.

Fetch one campaign: status, channel, content, audience, sending settings and contentID.

Create a campaign in draft. A regular email campaign needs content.email with subject, senderName and an existing templateID; a regular SMS campaign needs content.sms with message and compliance text. Sending is a separate step (send_campaign).

Update a DRAFT campaign. Any other status answers 409 Conflict. sendingSettings is replaced wholesale — resend every field applicable to the chosen strategy.

Start sending a campaign, or schedule it according to its sendingSettings. This delivers real email or SMS to the campaign's audience.

Cancel a scheduled, started or paused campaign. Delivery stops; the campaign moves to the canceled status.

List the store's product catalog. Offset-paginated (not cursor-paginated like contacts and campaigns).

Fetch one product with its variants.

Add a product to the store's Omnisend catalog so it can be used in emails, automations and product-abandonment flows.

Replace a product wholesale. This is a PUT: every field you leave out is cleared upstream, so resend the full product.

Delete a product from the Omnisend catalog.

List the store's product categories. Offset-paginated.

Fetch one product category.

Create a product category that products can reference through categoryIDs.

List the store's automation workflows with their enabled state and timestamps.

List the store's email templates. A template id is what create_campaign's content.email.templateID expects.