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 Account Services API

The Account Services API from Return Path — 13 operation(s) for account services.

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

This API exposes 23 operations across 13 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.

23 operations 13 paths 1 schemas 4 DELETE10 GET5 POST4 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 Account Services 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 23

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

Account Services 23
GET
/2.0/accounts
Accounts
accountsAccounts → 200401403404429500
POST
/2.0/accounts
Create Account
accountsCreateAccount body → 200401403404429500
GET
/2.0/accounts/{accountId}
Account & Usage
accountsAccountUsage 1 param → 200401403404429500
PUT
/2.0/accounts/{userId}
Update Account
accountsUpdateAccount 1 param body → 200401403404429500
DELETE
/2.0/accounts/{userId}
Delete Account
accountsDeleteAccount 1 param → 404200401403429500
GET
/2.0/accounts/plans
Plan
accountsPlan → 200401403404429500
GET
/2.0/accounts/subscriptions/{subscriptionId}
Subscription
accountsSubscription 1 param → 200401403404429500
GET
/2.0/accounts/{accountId}/subscriptions/{subscriptionId}
Account Subscription
accountsAccountSubscription 2 params → 200401403404429500
GET
/2.0/accounts/{accountId}/users
Users
usersUsers 1 param → 200401403404429500
POST
/2.0/accounts/{accountId}/users
Create User
usersCreateUser 1 param body → 400404200401403429500
GET
/2.0/accounts/{accountId}/users/{userId}
User by ID
usersUserByID 2 params → 200401403404429500
PUT
/2.0/accounts/{accountId}/users/{userId}
Update User
usersUpdateUser 2 params body → 400200401403404429500
POST
/2.0/accounts/{accountId}/users/{userId}
Add User to Account
usersAddUserToAccount 2 params → 200401403404429500
DELETE
/2.0/accounts/{accountId}/users/{userId}
Delete User from Account
usersDeleteUserFromAccount 2 params → 404200400401403429500
GET
/2.0/accounts/{accountId}/sso
Retrieve SSO Token
usersRetrieveSSOToken 2 params → 200401403404429500
GET
/2.0/accounts/{accountId}/keys
API Keys
apiKeysAPIKeys 1 param → 200401403404429500
POST
/2.0/accounts/{accountId}/keys
Create API Key
apiKeysCreateAPIKey 1 param body → 200401403404429500
DELETE
/2.0/accounts/{accountId}/keys/{key}
Delete API Key
apiKeysDeleteAPIKey 2 params → 404200401403429500
PUT
/2.0/accounts/{accountId}/keys/{key}
Update API Key
apiKeysUpdateAPIKey 2 params body → 200401403404429500
GET
/2.0/accounts/{accountId}/webhooks
Webhook Endpoints
webhookEndpointsWebhookEndpoints 3 params → 200401403404429500
POST
/2.0/accounts/{accountId}/webhooks
Create Webhook Endpoint
webhookEndpointsCreateWebhookEndpoint 1 param body → 200401403404429500
PUT
/2.0/accounts/{accountId}/webhooks/{webhookKey}
Update Webhook Endpoint
webhookEndpointsUpdateWebhookEndpoint 2 params body → 200401403404429500
DELETE
/2.0/accounts/{accountId}/webhooks/{webhookKey}
Delete Webhook Endpoint
webhookEndpointsDeleteWebhookEndpoint 2 params → 404500200401403429

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-account-services-api-openapi.yml Raw ↑

Other APIs Return Path publishes across the network.

Return Path Apps & Integrations API
Return Path Certification API
Return Path Competitive Intel API
Return Path Engagement 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 Account Services 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.