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 Call Function API

The EXPERIMENTAL Call Function API from NEAR Protocol — 1 operation(s) for experimental call function.

NEAR Protocol EXPERIMENTAL Call Function 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 Call Function. 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 21 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 21 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 Call Function 1
POST
/EXPERIMENTAL_call_function
EXPERIMENTAL call function
EXPERIMENTAL_call_function body → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are JsonRpcRequest_for_EXPERIMENTAL_call_function (4 properties), RpcCallFunctionResponse (4 properties), RpcCallFunctionRequest (3 properties), JsonRpcResponse_for_RpcCallFunctionResponse_and_RpcCallFunctionError (2 properties). Each schema is shown below with its type and property counts.

RpcCallFunctionError
FunctionCallError
Serializable version of near-vm-runner::FunctionCallError. Must never reorder/remove elements, can only add new variants at the end (but do that very carefully…
Finality
string
Different types of finality.
JsonRpcResponse_for_RpcCallFunctionResponse_and_RpcCallFunctionError
object
2 properties 2 required
RpcRequestValidationErrorKind
PrepareError
Error that can occur while preparing or executing Wasm smart-contract.
BlockReference
InternalError
WasmTrap
A kind of a trap happened during execution of a binary
CompilationError
SyncCheckpoint
string
FunctionArgs
string
This type is used to mark function arguments. NOTE: The main reason for this to exist (except the type-safety) is that the value is transparently serialized an…
CryptoHash
string
ErrorWrapper_for_RpcCallFunctionError
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…
BlockId
HostError
RpcCallFunctionResponse
object
A result returned by contract method
4 properties 4 required
JsonRpcRequest_for_EXPERIMENTAL_call_function
object
4 properties 4 required
RpcCallFunctionRequest
object
3 properties 3 required
MethodResolveError
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-experimental-call-function-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 Changes API
NEAR Protocol EXPERIMENTAL Changes In Block API
NEAR Protocol EXPERIMENTAL Congestion Level API
NEAR Protocol EXPERIMENTAL Genesis Config API
Where this information came from

This is an independent, third-party profile of NEAR Protocol EXPERIMENTAL Call Function 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.