Evervault Core API
The Core API from Evervault — 9 operation(s) for core.
Evervault Core API is one of 12 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.1.0, at version 0.0.1.
Requests are made against a single base URL, https://api.evervault.com.
Metadata
The identity and technical contract details declared by the specification.
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.
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.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Evervault 11
Other APIs Evervault publishes across the network.