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 Engagement API

The Engagement API from Return Path — 35 operation(s) for engagement.

Return Path Engagement 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 Engagement. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 38 operations across 35 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.

38 operations 35 paths 1 schemas 2 DELETE33 GET2 POST1 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 Engagement 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 38

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

Engagement 38
GET
/2.0/analytics/events/read
Detailed Read Events
engagementOverviewDetailedReadEvents → 200401403404429500
GET
/2.0/analytics/events/click
Detailed Click Events
engagementOverviewDetailedClickEvents → 200401403404429500
GET
/2.0/analytics/events/forward
Detailed Forward Events
engagementOverviewDetailedForwardEvents → 200401403404429500
GET
/2.0/analytics/events/print
Detailed Print Events
engagementOverviewDetailedPrintEvents → 200401403404429500
GET
/2.0/analytics/distribution/desktop
Platform Recipients
engagementOverviewPlatformRecipients → 200401403404429500
GET
/2.0/analytics/engagement/activity
Recent Activity
engagementOverviewRecentActivity → 200401403404429500
GET
/2.0/analytics/distribution
Platform Distribution
engagementOverviewPlatformDistribution → 200401403404429500
GET
/2.0/analytics/events
Detailed Events
engagementOverviewDetailedEvents → 200401403404429500
GET
/2.0/analytics/engagement
Overview
engagementOverviewOverview → 200401403404429500
GET
/2.0/analytics/audience/sources
Data Sources
audienceExplorerDataSources 1 param → 200401403404429500
GET
/2.0/analytics/audience/providers
Mailbox Providers
audienceExplorerMailboxProviders 2 params → 200401403404429500
GET
/2.0/analytics/audience/pixels
Pixels
audienceExplorerPixels 2 params → 200401403404429500
GET
/2.0/analytics/audience/platforms
Platforms
audienceExplorerPlatforms → 200401403404429500
GET
/2.0/analytics/audience/countries
Countries
audienceExplorerCountries 2 params → 200401403404429500
GET
/2.0/analytics/audience/regions
Regions
audienceExplorerRegions 2 params → 200401403404429500
GET
/2.0/analytics/audience/timezones
Time Zones
audienceExplorerTimeZones 2 params → 200401403404429500
GET
/2.0/analytics/audience/enthusiasm
Enthusiasm
audienceExplorerEnthusiasm → 200401403404429500
GET
/2.0/analytics/audience/timeofday
Time of Day
audienceExplorerTimeOfDay → 200401403404429500
GET
/2.0/analytics/audience/clients
Clients
audienceExplorerClients 2 params → 200401403404429500
GET
/2.0/analytics/audience/devices
Recipient Devices
audienceExplorerRecipientDevices 2 params → 200401403404429500
GET
/2.0/analytics/audience/recipients
Top Recipients
audienceExplorerTopRecipients 2 params → 200401403404429500
GET
/2.0/analytics/delivery
Overview
deliveryInsightsOverview → 200401403404429500
GET
/2.0/analytics/delivery/activity
Recent Activity
deliveryInsightsRecentActivity → 200401403404429500
GET
/2.0/analytics/delivery/sources
Data Sources
deliveryInsightsDataSources → 200401403404429500
GET
/2.0/analytics/delivery/providers
Mailbox Providers
deliveryInsightsMailboxProviders 1 param → 200401403404429500
GET
/2.0/analytics/delivery/todomains
Recipient Domains (to-domains)
deliveryInsightsRecipientDomainsToDomains 1 param → 200401403404429500
GET
/2.0/analytics/delivery/ips
IP Performance
deliveryInsightsIPPerformance 1 param → 200401403404429500
GET
/2.0/analytics/delivery/filtered
Filtered Messages
deliveryInsightsFilteredMessages → 200401403404429500
GET
/2.0/analytics/delivery/nondeliveries
Non-Deliveries
deliveryInsightsNonDeliveries 1 param → 200401403404429500
GET
/2.0/analytics/pixels
Pixels
analyticsSettingsPixels 1 param → 200401403404429500
POST
/2.0/analytics/pixels
Create Pixel
analyticsSettingsCreatePixel body → 200401403404429500
GET
/2.0/analytics/pixels/providers
Pixels: Providers
analyticsSettingsPixelsProviders → 200401403404429500
GET
/2.0/analytics/pixels/{pixelId}/code
Tracking Code by Pixel ID
analyticsSettingsTrackingCodeByPixelID 4 params → 200401403404429500
DELETE
/2.0/analytics/pixels/{pixelId}
Delete Pixel
analyticsSettingsDeletePixel 1 param → 200401403404429500
GET
/2.0/analytics/domains
Custom Domains
analyticsSettingsCustomDomains → 200401403404429500
POST
/2.0/analytics/domains
Create Domain
analyticsSettingsCreateDomain body → 400200401403404429500
PUT
/2.0/analytics/domains/{domainId}
Verify Domain
analyticsSettingsVerifyDomain 1 param → 400200401403404429500
DELETE
/2.0/analytics/domains/{domainId}
Delete Domain
analyticsSettingsDeleteDomain 1 param → 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-engagement-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 Inbox Placement 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 Engagement 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.