Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Evervault Acquirers API

The Acquirer API allows you to enroll Acquirer details with Card Networks to enable use of other payment APIs such as [3D Secure](#3d-secure).

Evervault Acquirers API is one of 12 APIs that Evervault publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Acquirers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 0.0.1.

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

5 operations 2 paths 1 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.0.1
Base URL
https://api.evervault.com
Authentication
HTTP Basic, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Evervault Acquirers API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (ApiKey). It accepts HTTP bearer tokens (RunToken) (TokenAuth). It accepts HTTP bearer tokens (Token) (ClientSideToken).

  • ApiKey — Authentication using an API key. The username is the App ID and the password is the Api Key.
  • TokenAuth — Authentication using a short lived run token that you can share with clients. The Authorization header must be formatted as follow: "RunToken "
  • ClientSideToken — Authentication using a short lived token that you can share with clients. The Authorization header must be formatted as follow: "Token "

Paths & Operations 5

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

Acquirers 5

The Acquirer API allows you to enroll Acquirer details with Card Networks to enable use of other payment APIs such as [3D Secure](3d-secure).

POST
/payments/acquirers
Create an Acquirer
createAcquirer body → 201
GET
/payments/acquirers
List Acquirers
listAcquirers 2 params → 200
GET
/payments/acquirers/{acquirer_id}
Retrieve an Acquirer
getAcquirer 1 param → 200
PATCH
/payments/acquirers/{acquirer_id}
Update an Acquirer
updateAcquirer 1 param body → 200
DELETE
/payments/acquirers/{acquirer_id}
Delete an Acquirer
deleteAcquirer 1 param → 204

Schemas 1

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

AcquirerConfiguration
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

evervault-acquirers-api-openapi.yml Raw ↑

Other APIs Evervault publishes across the network.

Evervault 3D Secure API
Evervault Card Account Updates API
Evervault Client Tokens API
Evervault Core API
Evervault Functions API
Evervault Insights API
Evervault Merchants API
Evervault Network Tokens API
Evervault Payments API
Evervault Relays API
Evervault Webhooks API