How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Customer.io ESP Suppression API

If you use Customer.io as your email service provider (ESP), these endpoints help you retrieve information about email addresses suppressed directly by the ESP. ESP-based suppressions are different from suppression in Customer.io: these are addresses that the ESP suppressed automatically because a message bounced, a customer requested they not be contacted again, etc. These are _not_ addresses that you deleted and suppressed either in our UI or through [the API](#operation/suppress).

Customer.io ESP Suppression API is one of 42 APIs that Customer.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ESP Suppression. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 4 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.customer.io, https://api-eu.customer.io.

5 operations 4 paths 0 schemas 1 DELETE3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://track.customer.io
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Customer.io ESP Suppression API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (Bearer-Auth). It accepts HTTP bearer tokens (sa_live_) (ServiceAccount-Auth). It accepts HTTP bearer tokens (bearerAuth).

  • Bearer-Auth — The App API uses a bearer authentication scheme. You can generate a bearer token, known as an App API Key, with a defined scope in [your account settings](http…
  • ServiceAccount-Auth — Transactional send endpoints (/v1/send/email, /v1/send/push, /v1/send/sms, /v1/send/inapp, /v1/send/inboxmessage) also accept a service-account bearer token, p…
  • bearerAuth — API key passed as a Bearer token

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

ESP Suppression 5

If you use Customer.io as your email service provider (ESP), these endpoints help you retrieve information about email addresses suppressed directly by the ESP. ESP-based suppress…

GET
/v1/esp/search_suppression/{email_address}
Look up an ESP-suppressed address
getSuppression 1 param → 200429
GET
/v1/esp/suppression/{suppression_type}
Get ESP-suppressed emails by type
getSuppressionByType 4 params → 200429
GET
/v1/esp/domains/{domain_name}/suppression/{suppression_type}
Get ESP-suppressed emails by domain
getDomainSuppressionsByType 5 params → 200429
DELETE
/v1/esp/suppression/{suppression_type}/{email_address}
Un-suppress an ESP-suppressed address
deleteSuppression 2 params → 204429
POST
/v1/esp/suppression/{suppression_type}/{email_address}
Suppress an email at the ESP
postSuppression 2 params → 200429

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

customer-io-esp-suppression-api-openapi.yml Raw ↑

Other APIs Customer.io publishes across the network.

Customer.io Track API
Customer.io Activities API
Customer.io Alias API
Customer.io Batch API
Customer.io Broadcasts API
Customer.io Campaigns API
Customer.io Collections API
Customer.io Customers API
Customer.io Exports API
Customer.io Group API
Customer.io Identify API
Customer.io Messages API
Where this information came from

This is an independent, third-party profile of Customer.io ESP Suppression API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.