Skip to main content

Chimes

Chimes are the SMS and email messages your business sends through Inttegro: receipts, delivery updates, reminders, and other customer notifications. Send one message now, schedule it for later, or broadcast it to an audience, then use its delivery status when a customer needs help. For one-time passwords, use the OTP API instead.

Operations

The chime object

A Chime is one notification for one recipient. It records the message, recipient, sender, and delivery status.

Properties

  • Name
    created_at
    Type
    timestamp
    Required
    required
    Description

    When this Chime was created for delivery.

  • Name
    customer_id
    Type
    string
    Description

    Saved customer used to resolve the recipient when the Chime was sent from a customer record. Omitted for inline recipients.

  • custom_dataobjectClick or tap to expand

    Your own key-value string pairs for custom data and tracking. Store user IDs, session identifiers, campaign tags, or any context you need for reconciliation and analytics.

  • emailobjectEmail content and safety scan result. Present when the Chime is sent by email.Click or tap to expand
    • Name
      from
      Type
      object
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Description
        Sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Additional email headers after validation.
    • Name
      html
      Type
      string|null
      Description
      HTML body before delivery-specific rendering.
    • Name
      reply_to
      Type
      object
      View reply_to attributesClick or tap to expand
      Mailbox that receives replies.
      • Name
        address
        Type
        string
        Description
        Reply-to email address.
      • Name
        name
        Type
        string
        Description
        Optional reply-to display name.
    • Name
      safety
      Type
      object
      View safety attributesClick or tap to expand
      Result of the email content safety scan.
      • Name
        content_hash
        Type
        string
        Description
        Hash of the content that was scanned.
      • Name
        normalized_text
        Type
        string
        Description
        Normalized plain-text body used by the scan.
      • Name
        quarantine_notes
        Type
        string|null
        Description
        Additional context when content is quarantined.
      • Name
        reason_codes
        Type
        array
        Description
        Machine-readable reasons for a non-allowed result.
      • Name
        sanitized_html
        Type
        string|null
        Description
        Sanitized HTML used for delivery, when available.
      • Name
        scanner
        Type
        string
        Description
        Safety scanner that produced the result.
      • Name
        status
        Type
        enum
        Description
        allowed, rejected, or quarantined.
    • Name
      schema
      Type
      object
      View schema attributesClick or tap to expand
      Schema.org markup generated for supported messages.
      • Name
        json_ld
        Type
        object
        View json_ld detailsClick or tap to expand
        Schema.org JSON-LD inserted into the HTML email.
      • Name
        kind
        Type
        enum
        Description
        gmail_view_action, schema_org_invoice, or schema_org_order.
    • Name
      subject
      Type
      string
      Description
      Email subject.
    • Name
      text
      Type
      string
      Description
      Plain-text email body.
  • Name
    full_message
    Type
    string
    Required
    required
    Description

    Rendered SMS content. This is an empty string for email Chimes, whose content is returned in the email object instead.

  • Name
    id
    Type
    string
    Required
    required
    Description

    Unique identifier for this Chime—use it for lookups, delivery tracking, and reconciliation.

  • Name
    idempotency_key
    Type
    string
    Description

    Request key associated with the Chime.

  • Name
    purpose
    Type
    string
    Description

    Application-defined category for this Chime. Omitted when it was not provided.

  • recipientobjectrequiredRecipient contact information.Click or tap to expand
    • Name
      email
      Type
      object
      View email attributesClick or tap to expand
      Present when recipient type is email.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Email address.
    • Name
      name
      Type
      string
      Description
      Recipient name for personalization.
    • Name
      phone
      Type
      object
      View phone attributesClick or tap to expand
      Present when recipient type is phone.
      • Name
        number
        Type
        string
        Required
        required
        Description
        Phone number in international format.
    • Name
      type
      Type
      enum
      Required
      required
      Description
      Contact type: phone or email.
  • Name
    sender_id
    Type
    string
    Required
    required
    Description

    Sender identifier used for SMS. Email senders are returned in email.from.

  • transmissionobjectTransmission details and delivery status. Omitted until a transmission exists.Click or tap to expand
    • Name
      address
      Type
      string
      Required
      required
      Description
      Resolved destination address used for the transmission.
    • Name
      created_at
      Type
      timestamp
      Required
      required
      Description
      When this transmission was initiated.
    • Name
      delivered_at
      Type
      timestamp
      Description
      When the message was delivered to the recipient. Omitted until delivery is confirmed.
    • Name
      email_events
      Type
      array
      View email_events attributesClick or tap to expand
      Recorded email delivery events.
      • Name
        bounce_sub_type
        Type
        string
        Description
        More specific bounce classification, when available.
      • Name
        bounce_type
        Type
        string
        Description
        Bounce classification, when available.
      • Name
        complaint_sub_type
        Type
        string
        Description
        More specific complaint classification, when available.
      • Name
        id
        Type
        string
        Required
        required
        Description
        Unique event identifier.
      • Name
        occurred_at
        Type
        timestamp
        Required
        required
        Description
        When the delivery event occurred.
      • Name
        provider
        Type
        string
        Required
        required
        Description
        Delivery service that reported the event.
      • Name
        provider_message_id
        Type
        string
        Required
        required
        Description
        Message identifier reported with the event.
      • Name
        reason
        Type
        string
        Description
        Human-readable event reason, when available.
      • Name
        reason_code
        Type
        string
        Description
        Machine-readable event reason, when available.
      • Name
        recipient
        Type
        string
        Description
        Recipient reported with the event, when available.
      • Name
        source
        Type
        string
        Description
        Source of the event, when available.
      • Name
        suppress_recipient
        Type
        boolean
        Description
        Whether future delivery to the recipient should be suppressed.
      • Name
        temporary
        Type
        boolean
        Description
        Whether the reported condition is temporary.
      • Name
        type
        Type
        string
        Required
        required
        Description
        Delivery event type.
    • Name
      email_failure_code
      Type
      string
      Description
      Email failure code. Omitted unless one is recorded.
    • Name
      email_failure_reason
      Type
      string
      Description
      Human-readable email failure reason. Omitted unless one is recorded.
    • Name
      email_status
      Type
      string
      Description
      Current email-specific delivery outcome. Omitted for non-email transmissions or until one is recorded.
    • Name
      error
      Type
      string
      Description
      Transmission error. Omitted unless an error is recorded.
    • Name
      failed_at
      Type
      timestamp
      Description
      When the transmission failed. Omitted unless status is failed.
    • Name
      gateway
      Type
      string
      Required
      required
      Description
      Delivery service selected for this transmission.
    • Name
      gateway_message_id
      Type
      string
      Description
      Message identifier returned by the delivery service. Omitted until one is available.
    • Name
      id
      Type
      string
      Required
      required
      Description
      Transmission identifier.
    • Name
      initialized_at
      Type
      timestamp
      Required
      required
      Description
      When this transmission was initialized.
    • Name
      last_email_event_at
      Type
      timestamp
      Description
      When the latest recorded email event occurred. Omitted until an event is recorded.
    • Name
      mechanism
      Type
      enum
      Required
      required
      Description
      Transmission mechanism: sms or email.
    • Name
      sent_at
      Type
      timestamp
      Description
      When the message was handed off for delivery. Omitted until it is sent.
    • Name
      sent_via
      Type
      enum
      Description
      Delivery transport used—sms or email.
    • Name
      status
      Type
      string
      Required
      required
      Description
      Current transmission status—initialized, sent, delivered, or failed.
    • Name
      suppressed_at
      Type
      timestamp
      Description
      When delivery to the email recipient was suppressed. Omitted unless suppressed.
    • Name
      suppression_reason
      Type
      string
      Description
      Reason delivery to the email recipient was suppressed. Omitted unless suppressed.
POST/chimes/send

Send chime

Send one notification immediately. You can address it directly with a phone number or email address, or point to a saved customer and let Inttegro use that customer's phone number or email address.

Available through MCP

AI clients can use send_customer_sms or send_customer_template for this operation. Confirmed MCP actions still require explicit form confirmation before Inttegro changes state.

The MCP tool covers saved-customer SMS sends only; it does not expose email sends, inline recipients, schedules, or broadcasts.

Rules

  • Send either SMS or email in one request. SMS uses full_message or an SMS message_template; email uses email or an email message_template.
  • Address a saved customer with customer_id and transport, or provide an inline phone number or email address. Do not combine the two recipient shapes.
  • Inline email content requires subject, text, and from.address. HTML and custom headers are checked before delivery.
  • A stored template must be published for the same channel as the recipient.

Required attributes

  • recipientobjectrequiredWhere to send the message.Click or tap to expand
    • Name
      customer_id
      Type
      string
      Required
      required
      Description
      Required for saved-customer recipients. Pair this with transport.
    • Name
      email
      Type
      object
      Required
      required
      View email attributesClick or tap to expand
      Required when type is email.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Email address to notify.
    • Name
      name
      Type
      string
      Description
      Optional recipient name for inline recipients.
    • Name
      phone
      Type
      object
      Required
      required
      View phone attributesClick or tap to expand
      Required when type is phone.
      • Name
        number
        Type
        string
        Required
        required
        Description
        Phone number to notify.
    • Name
      transport
      Type
      enum
      Required
      required
      Description
      Required for saved-customer recipients. Use sms to send to the customer's phone number or email to send to the customer's email address.
    • Name
      type
      Type
      enum
      Required
      required
      Description
      Required for inline recipients. Use phone or email.

Optional attributes

  • custom_dataobjectClick or tap to expand

    Your own key-value string pairs for tracking and reconciliation.

  • Name
    full_message
    Type
    string
    Description

    Complete SMS message content to send. Use this only for phone/SMS recipients when you are not using message_template.

  • message_templateobjectStored template reference. Use this instead of full_message for SMS recipients, or instead of email for email recipients.Click or tap to expand
    • Name
      template_id
      Type
      string
      Required
      required
      Description
      ID of a published stored template. The template channel must match the resolved recipient transport.
    • Name
      variables
      Type
      object
      View variables detailsClick or tap to expand
      Values for the template variables. Required variables must be present and valid for their declared types.
  • Name
    purpose
    Type
    string
    Description

    Optional category for this notification, such as receipt, notification, marketing, or reminder.

  • request_metaobjectRequest-specific controls that do not change the notification.Click or tap to expand
    • Name
      idempotency_key
      Type
      string
      Description
      Optional request key.
  • Name
    sender_id
    Type
    string
    Description

    SMS sender identifier. If omitted, Inttegro uses your default sender. For email, configure the sender with email.from.

Email attributes

  • emailobjectInline email content. Required for email recipients unless you use message_template.Click or tap to expand
    • Name
      from
      Type
      object
      Required
      required
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Allowed sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Additional email headers validated before delivery.
    • Name
      html
      Type
      string
      Description
      Optional HTML body checked before delivery.
    • Name
      reply_to
      Type
      string
      Description
      Optional reply-to email address.
    • Name
      subject
      Type
      string
      Required
      required
      Description
      Email subject.
    • Name
      text
      Type
      string
      Required
      required
      Description
      Plain-text body.

To send a Chime to a saved customer, pass recipient.customer_id and choose which contact method to use:

{
"recipient": {
"customer_id": "cu_abc123def456",
"transport": "sms"
},
"full_message": "Your order has shipped."
}

To send email to an inline address, use recipient.type: "email" and include the top-level email object:

{
"recipient": {
"type": "email",
"email": {
"address": "[email protected]"
},
"name": "Gloria Kesewaa"
},
"email": {
"subject": "Your receipt from YourBrand",
"text": "Your receipt is ready. View it at https://yourbrand.example/receipts/or_123.",
"html": "<p>Your receipt is ready. <a href=\"https://yourbrand.example/receipts/or_123\">View receipt</a>.</p>",
"from": {
"name": "YourBrand",
"address": "[email protected]"
}
},
"purpose": "receipt"
}

To send with a stored template, use the generated template ID and keep variables inside the message_template object:

{
"recipient": {
"customer_id": "cu_abc123def456",
"transport": "sms"
},
"message_template": {
"template_id": "mtpl_WkPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYU",
"variables": {
"order_number": "OR-12345",
"tracking_url": "https://track.example.com/OR-12345"
}
}
}

The examples below use the saved-customer shape. If you want to address someone directly instead, replace transport and customer_id with type and the matching inline phone or email details.

Request

POST/chimes/send
curl https://api.inttegro.com/chimes/send \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"request_meta": {
"idempotency_key": "chime_ship_or_abc123"
},
"recipient": {
"customer_id": "cu_abc123def456",
"transport": "sms"
},
"full_message": "Your order #OR-12345 has been shipped and will arrive in 2-3 business days.",
"sender_id": "YourBrand",
"purpose": "shipping_update",
"custom_data": {
"order_id": "or_abc123",
"fulfillment_id": "ffl_xyz789"
}
}'
{
"chime": {
"id": "ch_WkPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYU",
"customer_id": "cu_abc123def456",
"created_at": "2030-12-10T10:30:00Z",
"full_message": "Your order #OR-12345 has been shipped and will arrive in 2-3 business days. Track at: https://track.example.com/OR-12345",
"recipient": {
"type": "phone",
"phone": {
"number": "+233544998605"
},
"name": "Gloria Kesewaa"
},
"sender_id": "YourBrand",
"purpose": "shipping_update",
"custom_data": {
"order_id": "or_abc123",
"fulfillment_id": "ffl_xyz789"
},
"transmission": {
"address": "+233544998605",
"created_at": "2030-12-10T10:30:00Z",
"gateway": "configured_gateway",
"id": "GvYUWkPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGv",
"initialized_at": "2030-12-10T10:30:00Z",
"mechanism": "sms",
"sent_at": "2030-12-10T10:30:05Z",
"sent_via": "sms",
"status": "sent"
}
}
}
POST/chimes/lookup

Lookup chime

Retrieve one Chime to see what was sent and whether it was delivered. This is useful when answering delivery questions or matching a notification to your own records.

Available through MCP

AI clients can use get_message for this operation. MCP read tools return minimized business data and do not change Inttegro state.

Required attributes

  • Name
    chime_id
    Type
    string
    Required
    required
    Description

    Unique identifier of the Chime to retrieve.

Request

POST/chimes/lookup
curl https://api.inttegro.com/chimes/lookup \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"chime_id": "ch_WkPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYU"
}'

Response

SDK versionv8.2.0
ChimeResponse {
chime: {},
}
POST/chimes/page

Page chimes

Browse sent Chimes, newest first. Filter by customer or exact phone number or email address to review one recipient's notification history.

Available through MCP

AI clients can use list_messages for this operation. MCP read tools return minimized business data and do not change Inttegro state.

Optional attributes

  • Name
    customer_id
    Type
    string
    Description

    Restrict the page to Chimes associated with this customer.

  • Name
    page_number
    Type
    integer
    Description

    1-based page index to fetch. Defaults to 1 and must stay between 1 and 10.

  • Name
    page_size
    Type
    integer
    Description

    Number of Chimes to return. Defaults to 256 and must stay between 1 and 256.

  • Name
    recipient
    Type
    string
    Description

    Restrict the page to Chimes whose recipient exactly matches this phone number or email address.

You can filter by recipient, customer_id, both, or neither.

The response size is the number of Chimes actually returned in chimes, not the requested page capacity.

Request

POST/chimes/page
curl https://api.inttegro.com/chimes/page \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"page_number": 1,
"page_size": 25,
"customer_id": "cu_abc123def456"
}'
POST/chimes/schedule

Schedule chime

Schedule one or more notifications for a future time. Every recipient in a schedule must use the same channel, so create separate schedules for SMS and email.

Rules

  • send_after must be in the future.
  • Use one content source: full_message or an SMS template for SMS; email or an email template for email.
  • Address each recipient as a saved customer or an inline contact, using the same shapes as Send chime.

Required attributes

  • recipientsarray<object>requiredOne or more recipients. Each item uses one of the recipient shapes below.Click or tap to expand
    • Name
      customer_id
      Type
      string
      Required
      required
      Description
      Required for a saved-customer recipient. Pair with transport.
    • Name
      email
      Type
      object
      Required
      required
      View email attributesClick or tap to expand
      Required for an inline email recipient.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Email address to notify.
    • Name
      name
      Type
      string
      Description
      Optional name for an inline recipient.
    • Name
      phone
      Type
      object
      Required
      required
      View phone attributesClick or tap to expand
      Required for an inline phone recipient.
      • Name
        number
        Type
        string
        Required
        required
        Description
        Phone number to notify.
    • Name
      transport
      Type
      enum
      Required
      required
      Description
      Required for a saved-customer recipient: sms or email.
    • Name
      type
      Type
      enum
      Required
      required
      Description
      Required for an inline recipient: phone or email.
  • Name
    send_after
    Type
    timestamp
    Required
    required
    Description

    Earliest time at which processing may begin. Actual dispatch can occur later.

Optional attributes

  • emailobjectInline email content. Required for email recipients unless you use message_template.Click or tap to expand
    • Name
      from
      Type
      object
      Required
      required
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Allowed sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Additional email headers validated before delivery.
    • Name
      html
      Type
      string
      Description
      Optional HTML body checked before delivery.
    • Name
      reply_to
      Type
      string
      Description
      Optional reply-to email address.
    • Name
      subject
      Type
      string
      Required
      required
      Description
      Email subject.
    • Name
      text
      Type
      string
      Required
      required
      Description
      Plain-text body.
  • Name
    full_message
    Type
    string
    Description

    Complete SMS message content to send when the scheduled time arrives. Use this only for SMS schedules when you are not using message_template.

  • message_templateobjectStored template reference. Use this instead of full_message for SMS schedules, or instead of email for email schedules.Click or tap to expand
    • Name
      template_id
      Type
      string
      Required
      required
      Description
      ID of a published stored template. The template channel must match the resolved recipient transport.
    • Name
      variables
      Type
      object
      View variables detailsClick or tap to expand
      Values for the template variables. Required variables must be present and valid for their declared types.
  • Name
    purpose
    Type
    string
    Description

    Optional category for this scheduled notification.

  • request_metaobjectRequest-specific controls that do not change the scheduled notification.Click or tap to expand
    • Name
      idempotency_key
      Type
      string
      Description
      Optional request key.
  • Name
    sender_id
    Type
    string
    Description

    SMS sender identifier. If omitted, Inttegro uses your default sender. For email, configure the sender with email.from.

Response attributes

  • Name
    created_at
    Type
    timestamp
    Required
    required
    Description

    When the schedule was created.

  • Name
    customer_ids
    Type
    array
    Description

    Saved customer IDs resolved for this schedule. Omitted when none were used.

  • emailobjectValidated email content. Omitted for SMS schedules.Click or tap to expand
    • Name
      from
      Type
      object
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Description
        Sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Validated email headers.
    • Name
      html
      Type
      string|null
      Description
      HTML body.
    • Name
      reply_to
      Type
      object
      View reply_to attributesClick or tap to expand
      Mailbox that receives replies.
      • Name
        address
        Type
        string
        Description
        Reply-to email address.
      • Name
        name
        Type
        string
        Description
        Optional reply-to display name.
    • Name
      safety
      Type
      object
      View safety attributesClick or tap to expand
      Email content safety result.
      • Name
        content_hash
        Type
        string
        Description
        Hash of the scanned content.
      • Name
        normalized_text
        Type
        string
        Description
        Normalized text used by the scan.
      • Name
        quarantine_notes
        Type
        string|null
        Description
        Quarantine context, when available.
      • Name
        reason_codes
        Type
        array
        Description
        Reasons for a non-allowed result.
      • Name
        sanitized_html
        Type
        string|null
        Description
        Sanitized HTML, when available.
      • Name
        scanner
        Type
        string
        Description
        Scanner that produced the result.
      • Name
        status
        Type
        enum
        Description
        allowed, rejected, or quarantined.
    • Name
      schema
      Type
      object
      View schema attributesClick or tap to expand
      Generated Schema.org markup.
      • Name
        json_ld
        Type
        object
        View json_ld detailsClick or tap to expand
        Generated JSON-LD.
      • Name
        kind
        Type
        enum
        Description
        Generated markup kind.
    • Name
      subject
      Type
      string
      Description
      Email subject.
    • Name
      text
      Type
      string
      Description
      Plain-text email body.
  • Name
    executed_at
    Type
    timestamp
    Description

    When execution began. Omitted until execution.

  • Name
    full_message
    Type
    string
    Required
    required
    Description

    Rendered SMS content. Empty for email schedules.

  • Name
    id
    Type
    string
    Required
    required
    Description

    Schedule ID used with the schedule lookup and cancellation endpoints.

  • Name
    idempotency_key
    Type
    string
    Description

    Request key associated with the schedule.

  • Name
    purpose
    Type
    string
    Description

    Optional message category. Omitted when it was not provided.

  • Name
    recipients
    Type
    array
    Description

    Resolved destination addresses.

  • Name
    send_after
    Type
    timestamp
    Required
    required
    Description

    Earliest requested delivery time.

  • Name
    sender_id
    Type
    string
    Required
    required
    Description

    SMS sender selected for the scheduled messages. For email, see email.from.

To schedule for saved customers, include recipients with customer_id and transport:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "sms" },
{ "customer_id": "cu_def456ghi789", "transport": "sms" }
],
"full_message": "Reminder: Your appointment starts tomorrow at 10 AM.",
"send_after": "2030-12-15T10:00:00Z",
"request_meta": {
"idempotency_key": "sched_appointment_cu_abc123_2025_12_15"
}
}

To schedule email for saved customers, set transport: "email" and provide the top-level email object:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "email" },
{ "customer_id": "cu_def456ghi789", "transport": "email" }
],
"email": {
"subject": "Your subscription renews tomorrow",
"text": "Your subscription renews tomorrow. Update billing at https://yourbrand.example/billing.",
"from": {
"address": "[email protected]"
}
},
"send_after": "2030-12-15T10:00:00Z",
"purpose": "reminder"
}

To schedule with a stored template, use the same message_template object shape used by Send chime:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "email" }
],
"message_template": {
"template_id": "mtpl_emailRenewal123",
"variables": {
"customer_name": "Gloria",
"renewal_date": "2030-12-16"
}
},
"send_after": "2030-12-15T10:00:00Z",
"purpose": "reminder"
}

The examples below mix both recipient shapes in the same request.

Request

POST/chimes/schedule
curl https://api.inttegro.com/chimes/schedule \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipients": [
{
"customer_id": "cu_abc123def456",
"transport": "sms"
},
{
"type": "phone",
"phone": {
"number": "+233501234567"
},
"name": "Backup Contact"
}
],
"full_message": "Reminder: Your subscription renews tomorrow. Visit https://example.com/billing to update payment details.",
"send_after": "2030-12-15T09:00:00Z",
"sender_id": "YourBrand",
"purpose": "reminder"
}'

Response

SDK versionv8.2.0
ScheduledChimeResponse {
scheduledChime: {},
}
POST/schedules/lookup

Lookup a scheduled chime

Check whether a scheduled notification has run. After execution, the response includes the Chime IDs created for successful recipients and any recipient-specific errors.

Required attributes

  • Name
    schedule_id
    Type
    string
    Required
    required
    Description

    The schedule ID returned when you created the scheduled Chime. Example: sch_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk.

Response attributes

  • Name
    chime_ids
    Type
    array
    Description

    IDs created when the schedule executes. Omitted when there are no created Chimes.

  • Name
    content
    Type
    string
    Required
    required
    Description

    Rendered SMS content. Empty for email schedules.

  • Name
    created_at
    Type
    timestamp
    Required
    required
    Description

    When the schedule was created.

  • Name
    customer_ids
    Type
    array
    Description

    Saved customer IDs resolved for this schedule. Omitted when none were used.

  • emailobjectValidated email content. Omitted for SMS schedules.Click or tap to expand
    • Name
      from
      Type
      object
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Description
        Sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Validated email headers.
    • Name
      html
      Type
      string|null
      Description
      HTML body.
    • Name
      reply_to
      Type
      object
      View reply_to attributesClick or tap to expand
      Mailbox that receives replies.
      • Name
        address
        Type
        string
        Description
        Reply-to email address.
      • Name
        name
        Type
        string
        Description
        Optional reply-to display name.
    • Name
      safety
      Type
      object
      View safety attributesClick or tap to expand
      Email content safety result.
      • Name
        content_hash
        Type
        string
        Description
        Hash of the scanned content.
      • Name
        normalized_text
        Type
        string
        Description
        Normalized text used by the scan.
      • Name
        quarantine_notes
        Type
        string|null
        Description
        Quarantine context, when available.
      • Name
        reason_codes
        Type
        array
        Description
        Reasons for a non-allowed result.
      • Name
        sanitized_html
        Type
        string|null
        Description
        Sanitized HTML, when available.
      • Name
        scanner
        Type
        string
        Description
        Scanner that produced the result.
      • Name
        status
        Type
        enum
        Description
        allowed, rejected, or quarantined.
    • Name
      schema
      Type
      object
      View schema attributesClick or tap to expand
      Generated Schema.org markup.
      • Name
        json_ld
        Type
        object
        View json_ld detailsClick or tap to expand
        Generated JSON-LD.
      • Name
        kind
        Type
        enum
        Description
        Generated markup kind.
    • Name
      subject
      Type
      string
      Description
      Email subject.
    • Name
      text
      Type
      string
      Description
      Plain-text email body.
  • errorsarray<object>Per-recipient execution errors. Omitted when there are no errors.Click or tap to expand
    • Name
      fix_code
      Type
      string
      Description
      Suggested remediation code.
    • Name
      recipient
      Type
      string
      Description
      Recipient that could not be processed.
    • Name
      type
      Type
      string
      Description
      Error classification.
  • Name
    executed_at
    Type
    timestamp
    Description

    When execution began. Omitted until execution.

  • Name
    id
    Type
    string
    Required
    required
    Description

    Unique schedule identifier.

  • Name
    idempotency_key
    Type
    string
    Description

    Request key associated with the schedule.

  • Name
    purpose
    Type
    string
    Description

    Optional message category. Omitted when it was not provided.

  • Name
    recipients
    Type
    array
    Required
    required
    Description

    Resolved destination addresses.

  • Name
    send_after
    Type
    timestamp
    Required
    required
    Description

    Earliest requested delivery time.

  • Name
    sender_id
    Type
    string
    Required
    required
    Description

    SMS sender selected for the scheduled messages. For email, see email.from.

Request

POST/schedules/lookup
curl https://api.inttegro.com/schedules/lookup \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"schedule_id": "sch_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk"
}'

Response

SDK versionv8.2.0
ScheduledChimeResponse {
scheduledChime: {},
}
POST/schedules/cancel

Cancel a scheduled chime

Stop a scheduled notification before delivery begins. Cancel it before send_after; once execution starts, some or all messages may already be on their way.

Required attributes

  • Name
    schedule_id
    Type
    string
    Required
    required
    Description

    The schedule ID to cancel. The schedule must not be completed or already canceled.

A successful response returns the same schedule lifecycle fields as Lookup a scheduled chime, plus canceled_at with the recorded cancellation time.

Request

POST/schedules/cancel
curl https://api.inttegro.com/schedules/cancel \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: cancel-schedule-kPvqTrqGsopu07wf" \
-d '{
"schedule_id": "sch_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk"
}'

Response

SDK versionv8.2.0
ScheduledChimeResponse {
scheduledChime: {},
}
POST/chimes/broadcast

Broadcast chimes

Send one message to many recipients. The response confirms that Inttegro accepted the broadcast, not that every recipient has received a Chime; use Lookup a broadcast to follow its progress.

Rules

  • All recipients must use the same channel. Create separate broadcasts for SMS and email.
  • SMS uses raw text or a published SMS template. Email uses inline email content or a published email template.
  • Address each recipient as a saved customer or an inline contact, using the same shapes as Send chime.
  • Each recipient receives a separate Chime, so delivery can be tracked individually.
  • Provide sender when you do not want it to be empty; broadcasts do not apply a default sender.

Required attributes

  • recipientsarray<object>requiredOne or more recipients. Each item uses one of the recipient shapes below.Click or tap to expand
    • Name
      customer_id
      Type
      string
      Required
      required
      Description
      Required for a saved-customer recipient. Pair with transport.
    • Name
      email
      Type
      object
      Required
      required
      View email attributesClick or tap to expand
      Required for an inline email recipient.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Email address to notify.
    • Name
      name
      Type
      string
      Description
      Optional name for an inline recipient.
    • Name
      phone
      Type
      object
      Required
      required
      View phone attributesClick or tap to expand
      Required for an inline phone recipient.
      • Name
        number
        Type
        string
        Required
        required
        Description
        Phone number to notify.
    • Name
      transport
      Type
      enum
      Required
      required
      Description
      Required for a saved-customer recipient: sms or email.
    • Name
      type
      Type
      enum
      Required
      required
      Description
      Required for an inline recipient: phone or email.

Optional attributes

  • emailobjectInline email content. Required for email recipients unless you use message_template.Click or tap to expand
    • Name
      from
      Type
      object
      Required
      required
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Required
        required
        Description
        Allowed sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Additional email headers validated before delivery.
    • Name
      html
      Type
      string
      Description
      Optional HTML body checked before delivery.
    • Name
      reply_to
      Type
      string
      Description
      Optional reply-to email address.
    • Name
      subject
      Type
      string
      Required
      required
      Description
      Email subject.
    • Name
      text
      Type
      string
      Required
      required
      Description
      Plain-text body.
  • message_templateobjectSMS content or stored template reference.Click or tap to expand
    • Name
      template_id
      Type
      string
      Required
      required
      Description
      ID of a published stored template. SMS broadcasts require an SMS template; email broadcasts require an email template.
    • Name
      variables
      Type
      object
      View variables detailsClick or tap to expand
      Values for the template variables. Required variables must be present and valid for their declared types.
  • Name
    purpose
    Type
    string
    Description

    Optional category for this broadcast.

  • request_metaobjectRequest-specific controls that do not change the broadcast audience or content.Click or tap to expand
    • Name
      idempotency_key
      Type
      string
      Description
      Optional request key.
  • Name
    sender
    Type
    string
    Description

    SMS sender identifier. Strongly recommended because broadcasts do not apply a default. For email, configure the sender with email.from.

Response attributes

  • Name
    content
    Type
    string
    Required
    required
    Description

    Rendered SMS content. Empty for email broadcasts.

  • Name
    created_at
    Type
    timestamp
    Required
    required
    Description

    When the broadcast was created.

  • Name
    customer_ids
    Type
    array
    Description

    Saved customer IDs resolved for this broadcast. Omitted when none were used.

  • emailobjectValidated email content. Omitted for SMS broadcasts.Click or tap to expand
    • Name
      from
      Type
      object
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Description
        Sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Validated email headers.
    • Name
      html
      Type
      string|null
      Description
      HTML body.
    • Name
      reply_to
      Type
      object
      View reply_to attributesClick or tap to expand
      Mailbox that receives replies.
      • Name
        address
        Type
        string
        Description
        Reply-to email address.
      • Name
        name
        Type
        string
        Description
        Optional reply-to display name.
    • Name
      safety
      Type
      object
      View safety attributesClick or tap to expand
      Email content safety result.
      • Name
        content_hash
        Type
        string
        Description
        Hash of the scanned content.
      • Name
        normalized_text
        Type
        string
        Description
        Normalized text used by the scan.
      • Name
        quarantine_notes
        Type
        string|null
        Description
        Quarantine context, when available.
      • Name
        reason_codes
        Type
        array
        Description
        Reasons for a non-allowed result.
      • Name
        sanitized_html
        Type
        string|null
        Description
        Sanitized HTML, when available.
      • Name
        scanner
        Type
        string
        Description
        Scanner that produced the result.
      • Name
        status
        Type
        enum
        Description
        allowed, rejected, or quarantined.
    • Name
      schema
      Type
      object
      View schema attributesClick or tap to expand
      Generated Schema.org markup.
      • Name
        json_ld
        Type
        object
        View json_ld detailsClick or tap to expand
        Generated JSON-LD.
      • Name
        kind
        Type
        enum
        Description
        Generated markup kind.
    • Name
      subject
      Type
      string
      Description
      Email subject.
    • Name
      text
      Type
      string
      Description
      Plain-text email body.
  • Name
    id
    Type
    string
    Required
    required
    Description

    Broadcast ID used with the broadcast lookup and cancellation endpoints.

  • Name
    idempotency_key
    Type
    string
    Description

    Request key associated with the broadcast.

  • Name
    purpose
    Type
    string
    Description

    Optional message category. Omitted when it was not provided.

  • Name
    recipients
    Type
    array
    Required
    required
    Description

    Resolved destination addresses.

  • Name
    send_after
    Type
    timestamp
    Required
    required
    Description

    Time at which asynchronous processing was queued.

  • Name
    sender_id
    Type
    string
    Required
    required
    Description

    SMS sender selected for the broadcast messages. For email, see email.from.

For SMS broadcasts, message_template may be a raw SMS string for legacy inline content or an object with template_id and variables for stored templates. For email broadcasts, message_template must be an object; raw string content is SMS-only.

To broadcast to saved customers, include recipients with customer_id and transport:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "email" },
{ "customer_id": "cu_def456ghi789", "transport": "email" }
],
"email": {
"subject": "Your order has shipped",
"text": "Your order has shipped. Track it at https://track.shop.example/abc123.",
"from": {
"address": "[email protected]"
}
},
"sender": "ShopBrand",
"request_meta": {
"idempotency_key": "broadcast_shipping_2025_12_15"
}
}

To broadcast an email-only campaign, use email recipients and provide the top-level email object:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "email" },
{
"type": "email",
"email": {
"address": "[email protected]"
},
"name": "Backup Contact"
}
],
"email": {
"subject": "Your order has shipped",
"text": "Your order #12345 has shipped. Track it at https://track.shop.example/abc123.",
"from": {
"address": "[email protected]"
}
},
"sender": "ShopBrand",
"purpose": "order_notification"
}

To broadcast with a stored template, pass message_template as an object:

{
"recipients": [
{ "customer_id": "cu_abc123def456", "transport": "email" },
{ "customer_id": "cu_def456ghi789", "transport": "email" }
],
"message_template": {
"template_id": "mtpl_emailShipping123",
"variables": {
"order_number": "OR-12345",
"tracking_url": "https://track.shop.example/OR-12345"
}
},
"sender": "ShopBrand",
"purpose": "order_notification"
}

The examples below mix both recipient shapes in the same request.

Request

POST/chimes/broadcast
curl https://api.inttegro.com/chimes/broadcast \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipients": [
{
"customer_id": "cu_abc123def456",
"transport": "email"
},
{
"type": "email",
"email": {
"address": "[email protected]"
},
"name": "Backup Contact"
}
],
"email": {
"subject": "Your order #12345 has shipped",
"text": "Your order #12345 has shipped. Track it at https://track.shop.com/abc123.",
"from": {
"address": "[email protected]"
}
},
"sender": "ShopName",
"purpose": "order_notification"
}'

Response

SDK versionv8.2.0
BroadcastResponse {
broadcast: {},
}
POST/broadcasts/lookup

Lookup a broadcast

Check a broadcast's progress. The response lists the Chimes created for successful recipients and any recipient-specific errors.

Required attributes

  • Name
    broadcast_id
    Type
    string
    Required
    required
    Description

    The broadcast ID returned when you created the broadcast. Example: brc_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk.

Response attributes

  • Name
    chime_ids
    Type
    array
    Description

    IDs created when the broadcast executes. Omitted when there are no created Chimes.

  • Name
    content
    Type
    string
    Required
    required
    Description

    Rendered SMS content. Empty for email broadcasts.

  • Name
    created_at
    Type
    timestamp
    Required
    required
    Description

    When the broadcast was created.

  • Name
    customer_ids
    Type
    array
    Description

    Saved customer IDs resolved for this broadcast. Omitted when none were used.

  • emailobjectValidated email content. Omitted for SMS broadcasts.Click or tap to expand
    • Name
      from
      Type
      object
      View from attributesClick or tap to expand
      Mailbox shown in the email From field.
      • Name
        address
        Type
        string
        Description
        Sender email address.
      • Name
        name
        Type
        string
        Description
        Optional sender display name.
    • Name
      headers
      Type
      object
      View headers detailsClick or tap to expand
      Validated email headers.
    • Name
      html
      Type
      string|null
      Description
      HTML body.
    • Name
      reply_to
      Type
      object
      View reply_to attributesClick or tap to expand
      Mailbox that receives replies.
      • Name
        address
        Type
        string
        Description
        Reply-to email address.
      • Name
        name
        Type
        string
        Description
        Optional reply-to display name.
    • Name
      safety
      Type
      object
      View safety attributesClick or tap to expand
      Email content safety result.
      • Name
        content_hash
        Type
        string
        Description
        Hash of the scanned content.
      • Name
        normalized_text
        Type
        string
        Description
        Normalized text used by the scan.
      • Name
        quarantine_notes
        Type
        string|null
        Description
        Quarantine context, when available.
      • Name
        reason_codes
        Type
        array
        Description
        Reasons for a non-allowed result.
      • Name
        sanitized_html
        Type
        string|null
        Description
        Sanitized HTML, when available.
      • Name
        scanner
        Type
        string
        Description
        Scanner that produced the result.
      • Name
        status
        Type
        enum
        Description
        allowed, rejected, or quarantined.
    • Name
      schema
      Type
      object
      View schema attributesClick or tap to expand
      Generated Schema.org markup.
      • Name
        json_ld
        Type
        object
        View json_ld detailsClick or tap to expand
        Generated JSON-LD.
      • Name
        kind
        Type
        enum
        Description
        Generated markup kind.
    • Name
      subject
      Type
      string
      Description
      Email subject.
    • Name
      text
      Type
      string
      Description
      Plain-text email body.
  • errorsarray<object>Per-recipient execution errors. Omitted when there are no errors.Click or tap to expand
    • Name
      fix_code
      Type
      string
      Description
      Suggested remediation code.
    • Name
      recipient
      Type
      string
      Description
      Recipient that could not be processed.
    • Name
      type
      Type
      string
      Description
      Error classification.
  • Name
    executed_at
    Type
    timestamp
    Description

    When execution began. Omitted until execution.

  • Name
    id
    Type
    string
    Required
    required
    Description

    Unique broadcast identifier.

  • Name
    idempotency_key
    Type
    string
    Description

    Request key associated with the broadcast.

  • Name
    purpose
    Type
    string
    Description

    Optional message category. Omitted when it was not provided.

  • Name
    recipients
    Type
    array
    Required
    required
    Description

    Resolved destination addresses.

  • Name
    send_after
    Type
    timestamp
    Required
    required
    Description

    Time at which asynchronous processing was queued.

  • Name
    sender_id
    Type
    string
    Required
    required
    Description

    SMS sender selected for the broadcast messages. For email, see email.from.

Request

POST/broadcasts/lookup
curl https://api.inttegro.com/broadcasts/lookup \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"broadcast_id": "brc_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk"
}'

Response

SDK versionv8.2.0
BroadcastResponse {
broadcast: {},
}
POST/broadcasts/cancel

Cancel a broadcast

Stop a broadcast that has not finished processing. Because delivery begins asynchronously, cancel as soon as possible; some recipients may already have received their Chimes.

Required attributes

  • Name
    broadcast_id
    Type
    string
    Required
    required
    Description

    The broadcast ID to cancel. The broadcast must not be completed or already canceled.

A successful response returns the same broadcast lifecycle fields as Lookup a broadcast, plus canceled_at with the recorded cancellation time.

Request

POST/broadcasts/cancel
curl https://api.inttegro.com/broadcasts/cancel \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: cancel-broadcast-kPvqTrqGsopu07wf" \
-d '{
"broadcast_id": "brc_kPvqTrqGsopu07wfC7ttoWqmfwt48ZW7BGvYUWk"
}'

Response

SDK versionv8.2.0
BroadcastResponse {
broadcast: {},
}

Stored message template references

Chime send, schedule, and broadcast requests can render a stored message template instead of accepting inline content. Use this shape when the content should come from a published reusable template:

{
"message_template": {
"template_id": "mtpl_receipt_ready",
"variables": {
"customer_name": "Gloria",
"receipt_url": "https://yourstore.example/receipts/or_123"
}
}
}

message_template.template_id must identify a published template. Supply every required variable using the type defined by that template. SMS templates can send only to SMS recipients, and email templates can send only to email recipients.

Provide exactly one content source for the resolved transport. For SMS sends and schedules, use either full_message or an SMS message_template; for SMS broadcasts, use message_template as either raw SMS text or a stored template object. For email sends, schedules, and broadcasts, use either email or an email message_template. Do not combine SMS content and email content in the same request.

Use Render a message template preview before sending production campaigns when variable values come from user or catalog data.