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

Evervault Core API

The Core API from Evervault — 9 operation(s) for core.

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

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

This API exposes 14 operations across 9 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

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

14 operations 9 paths 12 schemas 2 DELETE4 GET1 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.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 Core 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 14

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

Core 14
POST
/encrypt
Encrypt
encrypt body → 200
POST
/decrypt
Decrypt
decrypt body → 200
POST
/inspect
Inspect
inspect body → 200
POST
/functions/{function_name}/runs
Run a Function
createFunctionRun 1 param body → 200202408409
POST
/client-side-tokens
Create a Client Token
create-client-side-token body → 201
POST
/relays
Create a Relay
createRelay body → 201
GET
/relays
List all Relays
listRelays → 200
GET
/relays/{id}
Retrieve a Relay
fetchRelay 1 param → 200
PATCH
/relays/{id}
Updates a Relay
updateRelay 1 param body → 200
DELETE
/relays/{id}
Delete a Relay
deleteRelay 1 param → 202
POST
/relays/{relay_id}/custom-domains
Create a Custom Domain
createCustomDomain 1 param body → 201
GET
/relays/{relay_id}/custom-domains
List all Custom Domains
fetchCustomDomainsForRelay 1 param → 200
GET
/relays/{relay_id}/custom-domains/{id}
Retrieve a Custom Domain
retrieveCustomDomain 2 params → 200
DELETE
/relays/{relay_id}/custom-domains/{id}
Delete a Custom Domain
deleteCustomDomain 2 params → 202

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Relay (9 properties), CardMetadata (8 properties), CustomDomain (7 properties), FunctionRun (5 properties). Each schema is shown below with its type and property counts.

CustomDomain
object
7 properties
FunctionRun
object
5 properties
ClientSideToken
object
4 properties
CardFunding
string
The card funding type specifies the method by which transactions are financed.
CardSegment
string
The card segment indicates the primary market or usage category of the card.
RelaySelection
object
3 properties 1 required
RelayAction
object
2 properties 2 required
Relay
object
9 properties
RelayRoute
object
4 properties 3 required
CardMetadata
object
Only present if category is card-number
8 properties 2 required
CardBrand
string
The card brand associated with the payment card.
Error
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

evervault-core-api-openapi.yml Raw ↑

Other APIs Evervault publishes across the network.

Evervault Payments API
Evervault Webhooks API
Evervault Evervault API
Where this information came from

This is an independent, third-party profile of Evervault Core 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.