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

The Merchants API from Evervault — 2 operation(s) for merchants.

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

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

This API exposes 5 operations across 2 paths, and defines 5 schemas. 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 5 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 Merchants 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.

Merchants 5
POST
/payments/merchants
Create a Merchant
createMerchant body → 201
GET
/payments/merchants
List Merchants
listMerchants 3 params → 200
GET
/payments/merchants/{merchant_id}
Retrieve a Merchant
getMerchant 1 param → 200
PATCH
/payments/merchants/{merchant_id}
Update a Merchant
updateMerchant 1 param body → 200
DELETE
/payments/merchants/{merchant_id}
Delete a Merchant
deleteMerchant 1 param → 204

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Merchant (10 properties), Address (6 properties), MerchantApplePay (1 property), MerchantNetworkTokenStatus (1 property). Each schema is shown below with its type and property counts.

MerchantNetworkTokenStatus
object
1 property
Address
object
6 properties 4 required
MerchantApplePay
object
1 property
CardBrand
string
The card brand associated with the payment card.
Merchant
object
10 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

evervault-merchants-api-openapi.yml Raw ↑

Other APIs Evervault publishes across the network.

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