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

Spektr Records API API

The Records API API from Spektr — 9 operation(s) for records api.

Spektr Records API API is one of 9 APIs that Spektr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Records API. 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 11 operations across 9 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v2.23.

Requests are made against a single base URL, https://ingest.spektr.com.

11 operations 9 paths 21 schemas 6 GET3 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2.23
Base URL
https://ingest.spektr.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Spektr Records API API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key).

  • x-api-key — You can generate API keys in settings from the developer dashboard.

Paths & Operations 11

Across 9 paths, the API surfaces 11 operations — 6 GET, 3 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Records API 11
POST
/v1/record/listOpenLoops
Get pending process runs
RecordController_listOpenLoops_v1 body → 200400404
GET
/v1/record/{spektrId}
Fetch customer record
RecordController_fetchRecord_v1 2 params → 200
PATCH
/v1/record/{spektrId}
Update customer record
RecordController_updateRecord_v1 1 param body → 200400404409
PATCH
/v2/record/{spektrId}
Update customer record v2
RecordController_updateRecordV2_v2 2 params body → 200400404409
GET
/v1/record/reference/{reference}
Fetch customer record by reference
RecordController_fetchRecordByReference_v1 3 params → 200
GET
/v1/record/{spektrId}/timeline
Get form submits for a given record
RecordController_getClientRecordFormSubmits_v1 1 param → 200
GET
/v1/record/bulk/fetch/api
Fetch records in bulk via API
RecordController_fetchRecordsApi_v1 6 params → 200
GET
/v1/record/bulk/fetch/s3
Fetch records in bulk via S3
RecordController_fetchRecordsS3_v1 6 params → 200
POST
/v1/record/relations
Create client record relations
RecordController_createClientRecordRelations_v1 body → 201400
PATCH
/v1/record/relations
Update client record relations
RecordController_updateClientRecordRelations_v1 body → 200400
GET
/v1/record/vendor-searches/{vendorSearchId}
Fetch a vendor search
RecordController_getVendorSearch_v1 1 param → 200404

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ProcessRunResponse (14 properties), CreateClientRecordRelationsResponseItemDto (12 properties), RecordResponse (11 properties), RecordFormSubmitResponse (9 properties). Each schema is shown below with its type and property counts.

ClientRecordId
object
2 properties 2 required
RecordProperties
object
4 properties
ProcessTriggerSource
object
4 properties 1 required
CreateClientRecordRelationsResponseDto
object
1 property 1 required
UpdateClientRecordRelationItemDto
object
6 properties 3 required
DataValidationError
object
2 properties 2 required
RecordFormSubmitResponse
object
9 properties
UpdateInputV2
object
4 properties
ProcessRunResponse
object
14 properties 8 required
UpdateInput
object
3 properties 1 required
RecordResponse
object
11 properties 6 required
RecordFormSubmitsResponse
object
1 property
CreateClientRecordRelationsResponseItemDto
object
12 properties 9 required
ProcessVersion
object
2 properties 2 required
DataParseError
object
2 properties 2 required
ClientRecordIds
object
1 property 1 required
RecordsResponse
object
3 properties
NotFoundError
object
2 properties 2 required
VendorSearchResponse
object
7 properties 6 required
CreateClientRecordRelationItemDto
object
7 properties 3 required
ClientRecordRelationEndpointDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spektr-records-api-api-openapi.yml Raw ↑

Other APIs Spektr publishes across the network.

Spektr Action API API
Spektr Events API API
Spektr Execution API API
Spektr Import API API
Spektr Orchestration API API
Spektr Transaction Definitions API
Spektr Transactions API
Spektr Workspace Fields API API
Where this information came from

This is an independent, third-party profile of Spektr Records API 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.