The Tableland Validator API is organized around REST. You can leverage these APIs to read directly from tables and compose data across them, and make calls to learn information about the node itself. Keep in mind that a node listens to mainnet chains and testnet chains separately such that there are separate Base URLs for each respective environment.

Setup

There are no required prerequisites, but it may be helpful to become familiar with HTTPie and cURL since the examples provided use these. Also, jq is an optional tool to help pipe the output from the API calls to a more human readable, “pretty” format (e.g., curl <url> | jq).

Base URLs

The following base URLs are supported:

Testnet chains ⇒ https://testnets.tableland.network/api/v1
Mainnet chains ⇒ https://tableland.network/api/v1

Endpoints

The following endpoints are available at the Base URL gateways above:

[/query](<https://textile.notion.site/Validator-API-e622f52063314c0db8dca75363ebb793>) ⇒ Write a SQL read query and get table data.
[/receipt/{chainId}/{transactionHash}](<https://textile.notion.site/Validator-API-e622f52063314c0db8dca75363ebb793>) ⇒ Retrieve on-chain transaction information regarding a table create or write query.
[/tables/{chainId}/{tableId}](<https://textile.notion.site/Validator-API-e622f52063314c0db8dca75363ebb793>) ⇒ Get table metadata and information.
[/health](<https://textile.notion.site/Validator-API-e622f52063314c0db8dca75363ebb793>) ⇒ Check if the validator is up and running.
[/version](<https://textile.notion.site/Validator-API-e622f52063314c0db8dca75363ebb793>) ⇒ Check version information about the validator daemon.