Skip to content

Register an RPC endpoint per network

List the workspace's networks and register RPC endpoints for them.

Updated View as Markdown

Auth: workspace token.

GET /v1/workspace/networks

List networks with the RPC tier currently answering for each. Scope: read. Returns 200.

{
  "networks": [
    {
      "slug": "ethereum",
      "name": "Ethereum",
      "chainId": 1,
      "vm": "evm",
      "rpcSource": "tenant"
    }
  ]
}
rpcSource Meaning
tenant A workspace-registered or tenant-configured endpoint answers
builtin wative-core’s shipped default answers. On unless your operator turned allowDefaultRpc off
none Nothing usable is configured for this network

A network reporting none will fail chain-touching calls with 409 and rpc_not_configured.

PUT /v1/workspace/networks/{slug}

Register an RPC endpoint for one network. Scope: write. Returns 200.

Request

{ "rpcUrl": "https://your-endpoint.example.com/eth" }

rpcUrl is 1–2048 characters. Unknown fields are rejected.

Response

{ "network": "ethereum", "rpcSource": "tenant" }

The URL passes an admission check before being stored; one the service refuses returns 400 with rpc_endpoint_rejected.

Errors

Status Code
400 invalid_body, invalid_slug, rpc_endpoint_rejected, unsupported_network
401 session_expired
403 scope_denied
404 account_not_found
409 rpc_not_configured
Navigation

Type to search…

↑↓ navigate↵ selectEsc close