Send API
Overview

Send API

The Send API queues transactional or application-generated email through PING8.

What the Send API screen is for

Use Developer > Send API to:

  • Create API templates.
  • Generate API keys.
  • Configure sender, subject, template, tracking, delivery engine, and IP allowlist.
  • Test API sends.
  • Copy curl examples.
  • Review send count, open rate, click rate, bounce rate, webhook, and status.

API endpoints

POST /api/batch_mail/api/send
POST /api/batch_mail/api/batch_send

For language clients, see SDK docs.

Before creating API keys

Confirm:

  • The sender domain verifies.
  • The API template has the correct sender, subject, and content.
  • The delivery engine is selected intentionally.
  • IP allowlist is planned if the key should only work from known servers.
  • Secrets will be stored in your application environment, not source code.

Typical setup flow

  1. Create an API template.
  2. Select sender, template body, tracking behavior, and delivery engine.
  3. Generate an API key.
  4. Restrict by IP when possible.
  5. Copy the curl example and replace the key with an environment variable.
  6. Send to one owned test recipient.
  7. Confirm API logs and delivery telemetry.

Response interpretation

The API returns queue acceptance and identifiers. It does not guarantee inbox placement. Use logs, lifecycle events, and webhooks to observe delivery.

Common mistakes

  • Committing an API key to source control.
  • Sending production traffic before domain verification is OK.
  • Retrying requests without understanding duplicate-email risk.
  • Using the campaign Send API path for bulk marketing without suppression review.
Failure DetailsCreate API Template