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

NEAR Protocol Next Light Client Block API

The Next Light Client Block API from NEAR Protocol — 1 operation(s) for next light client block.

NEAR Protocol Next Light Client Block API is one of 60 APIs that NEAR Protocol publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Next Light Client Block. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.

This API exposes 1 operation across 1 path, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 3.0.3.

Requests are made against 2 base URLs: https://api.fastnear.com, https://test.api.fastnear.com.

1 operations 1 paths 17 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.3
Base URL
https://rpc.mainnet.near.org
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Next Light Client Block 1
POST
/next_light_client_block
Returns the next light client block.
next_light_client_block body → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are BlockHeaderInnerLiteView (9 properties), RpcLightClientNextBlockResponse (6 properties), JsonRpcRequest_for_next_light_client_block (4 properties), ValidatorStakeViewV1 (3 properties). Each schema is shown below with its type and property counts.

RpcLightClientNextBlockRequest
object
1 property 1 required
RpcLightClientNextBlockResponse
object
A state for the current head of a light client. More info [here](https://nomicon.io/ChainSpec/LightClient).
6 properties
InternalError
BlockHeaderInnerLiteView
object
A part of a state for the current head of a light client. More info [here](https://nomicon.io/ChainSpec/LightClient).
9 properties 9 required
PublicKey
string
RpcRequestValidationErrorKind
AccountId
string
NEAR Account Identifier. This is a unique, syntactically valid, human-readable account identifier on the NEAR network. [See the crate-level docs for informatio…
RpcLightClientNextBlockError
JsonRpcResponse_for_RpcLightClientNextBlockResponse_and_RpcLightClientNextBlockError
object
2 properties 2 required
ErrorWrapper_for_RpcLightClientNextBlockError
ValidatorStakeViewV1
object
3 properties 3 required
Signature
string
NearToken
string
ValidatorStakeView
EpochId
Epoch identifier -- wrapped hash, to make it easier to distinguish. EpochId of epoch T is the hash of last block in T-2 EpochId of first two epochs is 0
CryptoHash
string
JsonRpcRequest_for_next_light_client_block
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-next-light-client-block-api-openapi.yml Raw ↑

Other APIs NEAR Protocol publishes across the network.

NEAR Protocol accounts API
NEAR Protocol Block API
NEAR Protocol Block Effects API
NEAR Protocol Broadcast Tx Async API
NEAR Protocol Broadcast Tx Commit API
NEAR Protocol Changes API
NEAR Protocol Chunk API
NEAR Protocol Client Config API
NEAR Protocol EXPERIMENTAL Call Function API
NEAR Protocol EXPERIMENTAL Changes API
NEAR Protocol EXPERIMENTAL Changes In Block API
NEAR Protocol EXPERIMENTAL Congestion Level API
Where this information came from

This is an independent, third-party profile of NEAR Protocol Next Light Client Block 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.