Salesforce

Salesforce Messaging API

Operations for creating and tracking email and SMS message sends, including triggered sends and transactional messages.

GitHub OpenAPI
Business capability
Digital Marketing Management BC-400.60

Operations 3

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /messaging/v1/email/messages Send a triggered email · Create an email send (triggered send) #
Ask an LLM
“How do I send a transactional email from a triggered send definition?”
“Can I personalize a triggered email differently for each recipient?”
Tell an agent
Send triggered email {definitionKey} to {recipients}.
Email {recipients} using definition {definitionKey} with attributes {attributes}.
POST /messaging/v1/sms/messages Send an SMS message · Create an SMS send #
Ask an LLM
“What's needed to text customers from a MobileConnect message definition?”
“Can an SMS send include personalized content for each recipient?”
Tell an agent
Send SMS definition {definitionKey} to {recipients}.
Text {recipients} with message {definitionKey} and attributes {attributes}.
GET /messaging/v1/email/messages/{messageKey} Check a triggered email's delivery status · Get email message send status #
Ask an LLM
“Was my triggered email delivered to the recipient?”
“Where can I see errors for one email send?”
Tell an agent
Get the delivery status of email message {messageKey}.
Check whether email send {messageKey} went through.

Documentation

📖
Documentation
https://developer.salesforce.com/docs/atlas.en-us.api_bulk_v2.meta/api_bulk_v2/
📖
APIReference
https://developer.salesforce.com/docs/atlas.en-us.api_bulk_v2.meta/api_bulk_v2/get_job_info.htm
📖
Authentication
https://developer.salesforce.com/docs/atlas.en-us.api_bulk_v2.meta/api_bulk_v2/bulk_api_2_0_security.htm
📖
Documentation
https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/
📖
GettingStarted
https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/ui_api_get_started.htm
📖
APIReference
https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/ui_api_resources_list.htm
📖
Documentation
https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/rest-api.html
📖
GettingStarted
https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/get-started-spec.html
📖
APIReference
https://developer.salesforce.com/docs/marketing/marketing-cloud/references/mc_rest_overview.html
📖
Authentication
https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/access-token-s2s.html
📖
Documentation
https://developer.salesforce.com/

Specifications

⚙
OpenAPI
https://artifacts.apis.io/salesforce/openapi/salesforce-messaging-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/salesforce/json-schema/salesforce-bulk-job-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/salesforce:salesforce-messaging-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

salesforce-messaging-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Salesforce Marketing Cloud REST Messaging API
  description: The Salesforce Marketing Cloud REST API provides access to Marketing Cloud resources including contacts, journeys, data extensions, triggered sends, and transactional messaging. It uses OAuth 2.0 for authentication and is the primary interface for programmatic Marketing Cloud integrations.
  version: v1
  contact:
    name: Salesforce Marketing Cloud Developers
    url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/rest-api.html
  license:
    name: Salesforce Developer Terms
    url: https://www.salesforce.com/company/legal/agreements/
servers:
- url: https://{subdomain}.rest.marketingcloudapis.com
  description: 'Marketing Cloud REST API endpoint. The subdomain is the tenant-specific subdomain for the Marketing Cloud account.

    '
  variables:
    subdomain:
      default: YOUR_SUBDOMAIN
      description: 'The Marketing Cloud tenant subdomain (also known as the MID-specific subdomain). Obtain this from the Marketing Cloud Setup > Company Settings > Account Info.

        '
security:
- BearerAuth: []
tags:
- name: Messaging
  description: Operations for creating and tracking email and SMS message sends, including triggered sends and transactional messages.
paths:
  /messaging/v1/email/messages:
    post:
      operationId: createEmailSend
      summary: Create an email send (triggered send)
      description: Creates and initiates a triggered email send to one or more recipients. Each send requires a message definition key referencing a triggered send definition configured in Marketing Cloud Email Studio. Supports personalization attributes and subscriber data overrides.
      tags:
      - Messaging
      requestBody:
        required: true
        description: Email message send configuration and recipients.
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/EmailMessage'
      responses:
        '202':
          description: 'Email send request accepted. The send is queued for processing.

            '
          content:
            application/json:
              schema:
                type: object
                properties:
                  requestId:
                    type: string
                    description: Unique ID for this send request.
                  responses:
                    type: array
                    description: 'Array of recipient-level responses indicating acceptance or errors.

                      '
                    items:
                      type: object
                      properties:
                        recipientSendId:
                          type: string
                          description: 'Unique ID for this recipient''s send. Use as the messageKey in status lookups.

                            '
                        hasErrors:
                          type: boolean
                          description: Whether this recipient's request had errors.
                        messages:
                          type: array
                          description: 'Error messages if hasErrors is true.

                            '
                          items:
                            type: string
        '400':
          description: Bad request. Invalid message definition or recipient data.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized. Invalid or expired access token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /messaging/v1/sms/messages:
    post:
      operationId: createSmsSend
      summary: Create an SMS send
      description: Creates and initiates an SMS message send to one or more recipients. Requires a message definition key referencing an SMS definition configured in Marketing Cloud MobileConnect. Supports personalization attributes for dynamic message content.
      tags:
      - Messaging
      requestBody:
        required: true
        description: SMS message send configuration and recipients.
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SMSMessage'
      responses:
        '202':
          description: SMS send request accepted and queued for processing.
          content:
            application/json:
              schema:
                type: object
                properties:
                  requestId:
                    type: string
                    description: Unique ID for this SMS send request.
                  responses:
                    type: array
                    description: Array of recipient-level send responses.
                    items:
                      type: object
                      properties:
                        recipientSendId:
                          type: string
                          description: Unique ID for this recipient's SMS send.
                        hasErrors:
                          type: boolean
                          description: Whether this recipient's request had errors.
        '400':
          description: Bad request. Invalid message definition or phone number format.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized. Invalid or expired access token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /messaging/v1/email/messages/{messageKey}:
    get:
      operationId: getMessageStatus
      summary: Get email message send status
      description: Retrieves the status of a triggered email send for a specific recipient using the messageKey (recipientSendId) returned when the send was created. Returns the current delivery status and any error details.
      tags:
      - Messaging
      parameters:
      - name: messageKey
        in: path
        required: true
        description: 'The unique message key (recipientSendId) returned when the email send was created.

          '
        schema:
          type: string
      responses:
        '200':
          description: Email message send status.
          content:
            application/json:
              schema:
                type: object
                properties:
                  eventCategoryType:
                    type: string
                    description: 'The delivery event type (e.g., SendReady, NotSent, Sent, Delivered, Bounced, Opened, Clicked).

                      '
                  timestamp:
                    type: string
                    format: date-time
                    description: The timestamp of the most recent status event.
                  subscriberKey:
                    type: string
                    description: The subscriber key of the recipient.
                  messageKey:
                    type: string
                    description: The unique message key for this send.
        '401':
          description: Unauthorized. Invalid or expired access token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Message not found for the specified message key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      description: An error response from the Marketing Cloud REST API.
      properties:
        message:
          type: string
          description: Human-readable description of the error.
        errorcode:
          type: integer
          description: Marketing Cloud numeric error code.
        documentation:
          type: string
          description: URL to documentation about this error.
    SMSMessage:
      type: object
      description: 'Configuration for a triggered SMS send to one or more recipients using a Marketing Cloud MobileConnect message definition.

        '
      required:
      - definitionKey
      - recipients
      properties:
        definitionKey:
          type: string
          description: 'The external key of the SMS message definition configured in Marketing Cloud MobileConnect.

            '
        recipients:
          type: array
          description: 'Array of recipients for this triggered SMS send.

            '
          items:
            type: object
            required:
            - contactKey
            - to
            properties:
              contactKey:
                type: string
                description: The subscriber key of the SMS recipient.
              to:
                type: string
                description: 'The recipient phone number in E.164 format (e.g., +15551234567).

                  '
              attributes:
                type: object
                description: 'Key-value pairs of personalization attributes for this recipient.

                  '
                additionalProperties: true
        attributes:
          type: object
          description: 'Default personalization attributes applied to all recipients unless overridden at the recipient level.

            '
          additionalProperties: true
    EmailMessage:
      type: object
      description: 'Configuration for a triggered email send to one or more recipients using a Marketing Cloud triggered send definition.

        '
      required:
      - definitionKey
      - recipients
      properties:
        definitionKey:
          type: string
          description: 'The external key of the triggered send definition configured in Marketing Cloud Email Studio.

            '
        recipients:
          type: array
          description: 'Array of recipients for this triggered email send. Each recipient can have individual attributes for personalization.

            '
          items:
            type: object
            required:
            - contactKey
            properties:
              contactKey:
                type: string
                description: The subscriber key of the email recipient.
              to:
                type: string
                format: email
                description: 'The recipient email address. Overrides the subscriber''s stored email address if provided.

                  '
              attributes:
                type: object
                description: 'Key-value pairs of personalization attributes for this recipient.

                  '
                additionalProperties: true
              messageKey:
                type: string
                description: 'A unique identifier for this specific recipient''s send. If not provided, one is generated automatically.

                  '
        attributes:
          type: object
          description: 'Default personalization attributes applied to all recipients unless overridden at the recipient level.

            '
          additionalProperties: true
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'OAuth 2.0 Bearer token obtained from the /v2/token endpoint. Include this token in the Authorization header as "Bearer {access_token}".

        '