Plunk

Plunk Transactional API

Send transactional email.

Documentation GitHub OpenAPI

Operations 1

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 /send Send a transactional email · Send a transactional email #

Ask an LLM

“How do I send a one-off transactional email with Plunk?”

“Can I send the same transactional email to several recipients at once?”

Tell an agent

Send {to} an email with subject {subject} and body {body}.

Email {to} from {from} with reply-to {reply}, subject {subject}, body {body}.

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/plunk-transactional-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

openapi: 3.2.0
info:
  title: Plunk Transactional API
  description: The Plunk REST API for the open-source email platform for SaaS.
  termsOfService: https://www.useplunk.com/legal/terms
  contact:
    name: Plunk Support
    url: https://docs.useplunk.com
  license:
    name: AGPL-3.0
    url: https://github.com/useplunk/plunk/blob/main/LICENSE
  version: '1.0'
servers:
- url: https://api.useplunk.com/v1
  description: Plunk hosted API
security:
- bearerAuth: []
tags:
- name: Transactional
  description: Send transactional email.
paths:
  /send:
    post:
      operationId: sendEmail
      tags:
      - Transactional
      summary: Send a transactional email
      description: Sends a single transactional email to one or more recipients using a secret API key. The body may be HTML or plain text. Optional fields allow overriding the sender, reply-to, custom headers, and attachments.
      security:
      - bearerAuth: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SendEmailRequest'
            example:
              to: user@example.com
              subject: Welcome to our app
              body: <p>Thanks for signing up!</p>
      responses:
        '200':
          description: Email accepted for delivery.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SendEmailResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '422':
          $ref: '#/components/responses/ValidationError'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  responses:
    RateLimited:
      description: Too many requests; the project rate limit was exceeded.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ValidationError:
      description: The request body failed validation.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Missing or invalid API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    SendEmailResponse:
      type: object
      properties:
        success:
          type: boolean
        emails:
          type: array
          items:
            type: object
            properties:
              contact:
                type: object
                properties:
                  id:
                    type: string
                  email:
                    type: string
              email:
                type: string
        timestamp:
          type: string
          format: date-time
    Error:
      type: object
      properties:
        success:
          type: boolean
          example: false
        code:
          type: integer
        error:
          type: string
        message:
          type: string
        time:
          type: integer
    SendEmailRequest:
      type: object
      required:
      - to
      - subject
      - body
      properties:
        to:
          description: Recipient email address, or an array of addresses.
          oneOf:
          - type: string
            format: email
          - type: array
            items:
              type: string
              format: email
        subject:
          type: string
          description: Email subject line.
        body:
          type: string
          description: Email body, as HTML or plain text.
        subscribed:
          type: boolean
          description: Whether the recipient is treated as a subscribed contact.
        name:
          type: string
          description: Display name to send from.
        from:
          type: string
          format: email
          description: Sender email address (must be a verified sender).
        reply:
          type: string
          format: email
          description: Reply-to email address.
        headers:
          type: object
          additionalProperties:
            type: string
          description: Custom email headers.
        attachments:
          type: array
          description: File attachments.
          items:
            type: object
            properties:
              filename:
                type: string
              content:
                type: string
                description: Base64-encoded file content.
              type:
                type: string
                description: MIME type of the attachment.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Plunk API key passed as a Bearer token. Use a secret key (sk_) for most endpoints; the /track endpoint additionally accepts a public key (pk_).