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

Return Path Inbox Placement API

The Inbox Placement API from Return Path — 17 operation(s) for inbox placement.

Return Path Inbox Placement API is one of 11 APIs that Return Path publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Inbox Placement. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 22 operations across 17 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.everest.validity.com/api.

22 operations 17 paths 1 schemas 2 DELETE17 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.everest.validity.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Return Path Inbox Placement API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-KEY (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Every API request requires the X-API-KEY header. The key is found in Everest account settings.

Paths & Operations 22

Across 17 paths, the API surfaces 22 operations — 2 DELETE, 17 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Inbox Placement 22
GET
/2.0/inbox/seeds
Seed List
seedListsSeedList body → 200401403404429500
PUT
/2.0/inbox/seeds
Update Seed List
seedListsUpdateSeedList body → 200401403404429500
GET
/2.0/inbox/seeds/providers
Regions & Providers
seedListsRegionsProviders → 200401403404429500
GET
/2.0/inbox/optimizer
All Lists
listOptimizerAllLists → 200401403404429500
POST
/2.0/inbox/optimizer
Create List
listOptimizerCreateList body → 200401403404429500
GET
/2.0/inbox/optimizer/{optimizerId}
List by ID
listOptimizerListByID 1 param → 200401403404429500
DELETE
/2.0/inbox/optimizer/{optimizerId}
Delete List
listOptimizerDeleteList 1 param → 200401403404429500
PUT
/2.0/inbox/optimizer/{optimizerId}
Apply List Weighting
listOptimizerApplyListWeighting 2 params → 200401403404429500
GET
/2.0/inbox/optimizer/{optimizerId}/domains/{domainId}
Domains by List
listOptimizerDomainsByList 2 params → 200401403404429500
GET
/2.0/inbox/tests
All Inbox Tests
inboxTestsAllInboxTests → 200401403404429500
GET
/2.0/inbox/tests/{testId}
Inbox Test by ID
inboxTestsInboxTestByID 1 param → 200401403404429500
DELETE
/2.0/inbox/tests/{testId}
Delete Test
inboxTestsDeleteTest 1 param → 200401403404429500
GET
/2.0/inbox/tests/{testId}/message
Inbox Test: Full Message
inboxTestsInboxTestFullMessage 1 param → 200401403404429500
GET
/2.0/inbox/tests/{testId}/providers
Inbox Test: All Providers
inboxTestsInboxTestAllProviders 1 param → 200401403404429500
GET
/2.0/inbox/tests/{testId}/providers/{providerId}
Inbox Test: Provider by ID
inboxTestsInboxTestProviderByID 2 params → 200401403404429500
GET
/2.0/inbox/tests/{testId}/providers/{providerId}/headers/{headerId}
Inbox Test: Headers by Mailbox ID
inboxTestsInboxTestHeadersByMailboxID 3 params → 200401403404429500
GET
/2.0/inbox/aggregates/region
Inbox Placement: Region
aggregateReportsInboxPlacementRegion → 200401403404429500
GET
/2.0/inbox/aggregates/b2b
Inbox Placement: B2B
aggregateReportsInboxPlacementB2B → 200401403404429500
GET
/2.0/inbox/aggregates/b2c
Inbox Placement: B2C
aggregateReportsInboxPlacementB2C → 200401403404429500
GET
/2.0/inbox/aggregates/fromdomain
Inbox Placement: From Domain
aggregateReportsInboxPlacementFromDomain → 200401403404429500
GET
/2.0/inbox/aggregates/fromaddress
Inbox Placement: From Address
aggregateReportsInboxPlacementFromAddress → 200401403404429500
GET
/2.0/inbox/health
Mailbox Provider Health
aggregateReportsMailboxProviderHealth → 200401403404429500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
Every 400-level response carries a status object describing the problem.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

return-path-inbox-placement-api-openapi.yml Raw ↑

Other APIs Return Path publishes across the network.

Return Path Account Services API
Return Path Apps & Integrations API
Return Path Certification API
Return Path Competitive Intel API
Return Path Engagement API
Return Path Infrastructure (DMARC) API
Return Path Legacy API (1.0) API
Return Path List Validation API
Return Path Reputation API
Return Path View Time Optimization API
Where this information came from

This is an independent, third-party profile of Return Path Inbox Placement 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.