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 EXPERIMENTAL View Code API

The EXPERIMENTAL View Code API from NEAR Protocol — 1 operation(s) for experimental view code.

NEAR Protocol EXPERIMENTAL View Code 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 EXPERIMENTAL View Code. 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 14 schemas. It is described by OpenAPI 3.2.0, at version 1.2.11.

Requests are made against the base URL https://rpc.mainnet.near.org.

1 operations 1 paths 14 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.11
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.

EXPERIMENTAL View Code 1
POST
/EXPERIMENTAL_view_code
EXPERIMENTAL view code
EXPERIMENTAL_view_code body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are RpcViewCodeResponse (4 properties), JsonRpcRequest_for_EXPERIMENTAL_view_code (4 properties), JsonRpcResponse_for_RpcViewCodeResponse_and_RpcViewCodeError (2 properties), RpcViewCodeRequest (1 property). Each schema is shown below with its type and property counts.

BlockReference
RpcViewCodeRequest
object
1 property 1 required
InternalError
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…
ErrorWrapper_for_RpcViewCodeError
SyncCheckpoint
string
BlockId
RpcViewCodeResponse
object
A view of the contract code.
4 properties 4 required
Finality
string
Different types of finality.
RpcViewCodeError
JsonRpcRequest_for_EXPERIMENTAL_view_code
object
4 properties 4 required
CryptoHash
string
RpcRequestValidationErrorKind
JsonRpcResponse_for_RpcViewCodeResponse_and_RpcViewCodeError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-experimental-view-code-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 EXPERIMENTAL View Code 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.