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

Adobe Suite Suppression API

The Suppression API from Adobe Suite — 7 operation(s) for suppression.

Adobe Suite Suppression API is one of 482 APIs that Adobe Suite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Suppression. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, release notes, and a getting-started guide.

This API exposes 13 operations across 7 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.1.

Requests are made against 2 base URLs: https://platform-stage.adobe.io/ajo, https://platform.adobe.io/ajo.

13 operations 7 paths 26 schemas 4 DELETE6 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.1
Base URL
https://image.adobe.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Adobe Suite Suppression API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — The authentication token to access the service.

Paths & Operations 13

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

Suppression 13
GET
/config/suppression/addresses
Query suppressed or allowed emails addresses
getAddressesId 9 params → 200
POST
/config/suppression/addresses
Add a suppressed or allowed email address
addAddressId 5 params body → 201
GET
/config/suppression/addresses/{email}
Query a specific suppressed or allowed email address
getEmailAddressId 6 params → 200
DELETE
/config/suppression/addresses/{email}
Delete a specific suppressed or allowed email address
deleteEmailAddressId 6 params → 204
GET
/config/suppression/domains
Query suppressed or allowed domains
getDomainsId 9 params → 200
POST
/config/suppression/domains
Add a suppressed or allowed domain
addDomainId 5 params body → 201
GET
/config/suppression/domains/{domain}
Query a specific suppressed or allowed domain
getDomainId 5 params → 200
DELETE
/config/suppression/domains/{domain}
Delete a specific suppressed or allowed domain
deleteDomainId 5 params → 204
POST
/config/suppression/uploads
Upload a CSV file of suppressed entities
uploadId 5 params body → 201
GET
/config/suppression/uploads
Fetch upload jobs
getUploadsId 8 params → 200
GET
/config/suppression/uploads/{jobId}
Query a specific upload job
getUploadJobId 5 params → 200
DELETE
/config/suppression/uploads/{jobId}
Delete a specific upload job.
deleteUploadJobId 5 params → 204
DELETE
/config/suppression/admin/{imsOrgId}/{sandboxId}
Delete all suppressions from a given sandbox-Id and IMS-Org-Id
deleteAllSuppressions 6 params → 202

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are uploads (11 properties), entityObject (9 properties), domainEntityObject (8 properties), addEntityObject (8 properties). Each schema is shown below with its type and property counts.

uploadStatus
string
The current state of the upload. Can be one of the following: Accepted: The file has been accepted and a jobId has ben created.
bounceState
object
2 properties
entityObject
object
9 properties 9 required
uploadListLink
object
2 properties 1 required
page
object
3 properties
addEmailAddress
object
3 properties 1 required
suppressionListLink
object
2 properties 1 required
uploads
object
11 properties
addDomain
object
3 properties 1 required
suppressionListResponse
object
uploadJob
object
3 properties
uploadListResponse
object
listType
string
bounceEvents
object
4 properties
domainSuppressionListResponse
object
hRefLink
object
1 property 1 required
status
string
uploadPage
object
3 properties
type
string
suppressionListAddResponse
object
suppressed
object
4 properties
domainEntityObject
object
8 properties 8 required
uploadPost
object
1 property
failedRecord
object
4 properties
addEntityObject
object
8 properties 8 required
client
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-suite-suppression-api-openapi.yml Raw ↑

Other APIs Adobe Suite publishes across the network.

Adobe Sign API
Adobe Experience Manager API
Adobe Stock API
Adobe Premiere Pro API
Adobe After Effects API
Adobe Target API
Adobe Campaign API
Adobe User Management API
Adobe I/O Events API
Adobe MCP Servers
Adobe Suite Accelerated Queries API
Adobe Suite Access Control Policies API
Where this information came from

This is an independent, third-party profile of Adobe Suite 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.