Evermuse ingestion API
Send data to Evermuse
Evermuse ingestion API is published by Evermuse on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ingestion. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.
This API exposes 3 operations across 3 paths, and defines 11 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://api.evermuse.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Evermuse ingestion API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as x-api-key (IngestApiKey).
IngestApiKey— Your API key, sent as the x-api-key header. Create one in Settings API Keys with api:write permission. Format: emsk...
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Send data to Evermuse
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are IngestRecord (13 properties), IngestBatchStatus (13 properties), Attachment (8 properties), Participant (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.