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

S2 Dev records API

Manage records

S2 Dev records API is one of 6 APIs that S2 Dev publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 2 paths, and defines 16 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://a.s2.dev/v1.

3 operations 2 paths 16 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://a.s2.dev/v1
Authentication
HTTP Bearer
License
MIT
Terms of Service
Resource Areas
1

Authentication & Security 1

S2 Dev records API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (access_token). By default, every request must be authenticated.

  • access_token — Bearer authentication header of the form Bearer , where is your access token.

Paths & Operations 3

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

records 3

Manage records

GET
/streams/{stream}/records
Read records.
read 11 params → 200400403404408409416
POST
/streams/{stream}/records
Append records.
append 3 params body → 200400403404408409412
GET
/streams/{stream}/records/tail
Check the tail.
check_tail 1 param → 200400403404408409

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are SequencedRecord (4 properties), AppendRecord (3 properties), AppendInput (3 properties), AppendAck (3 properties). Each schema is shown below with its type and property counts.

AppendInput
object
Payload of an append request.
3 properties 1 required
ReadEvent
FencingToken
string
PingEventData
object
2 properties 2 required
ReadBatch
object
2 properties 1 required
u64
integer
AppendConditionFailed
Aborted due to a failed condition.
Header
array
AppendAck
object
Success response to an append request.
3 properties 3 required
AppendRecord
object
Record to be appended to a stream.
3 properties
StreamPosition
object
Position of a record in a stream.
2 properties 2 required
TailResponse
object
1 property 1 required
ErrorInfo
object
2 properties 2 required
StreamNameStr
string
SequencedRecord
object
Record that is durably sequenced on a stream.
4 properties 2 required
Format
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

s2-dev-records-api-openapi.yml Raw ↑

Other APIs S2 Dev publishes across the network.

S2 Dev access-tokens API
S2 Dev basins API
S2 Dev locations API
S2 Dev metrics API
S2 Dev streams API
Where this information came from

This is an independent, third-party profile of S2 Dev records 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.