apiv1

Documentation

Overview

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Tableland Validator - OpenAPI 3.0 * * In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities: - Listen to on-chain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default). - Serve read-queries (e.g: SELECT * FROM foo_69_1) to the external world. - Serve state queries (e.g. list tables, get receipts, etc) to the external world. In the 1.0.0 release of the Tableland Validator API, we've switched to a design first approach! You can now help us improve the API whether it's by making changes to the definition itself or to the code. That way, with time, we can improve the API in general, and expose some of the new features in OAS3. * * API version: 1.0.0 * Contact: carson@textile.io * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

Index

• func GetTableById(w http.ResponseWriter, r *http.Request)
• func Health(w http.ResponseWriter, r *http.Request)
• func Index(w http.ResponseWriter, r *http.Request)
• func Logger(inner http.Handler, name string) http.Handler
• func NewRouter() *mux.Router
• func QueryByStatement(w http.ResponseWriter, r *http.Request)
• func ReceiptByTransactionHash(w http.ResponseWriter, r *http.Request)
• func Version(w http.ResponseWriter, r *http.Request)
• type Column
• type OneOfTableAttributesValue
• type Route
• type Routes
• type Schema
• type Table
• type TableAttributes
• type TransactionReceipt
• type VersionInfo

Functions

func GetTableById

func GetTableById(w http.ResponseWriter, r *http.Request)

func Health

func Health(w http.ResponseWriter, r *http.Request)

func Index

func Index(w http.ResponseWriter, r *http.Request)

func Logger

func Logger(inner http.Handler, name string) http.Handler

func NewRouter

func NewRouter() *mux.Router

func QueryByStatement

func QueryByStatement(w http.ResponseWriter, r *http.Request)

func ReceiptByTransactionHash

func ReceiptByTransactionHash(w http.ResponseWriter, r *http.Request)

func Version

func Version(w http.ResponseWriter, r *http.Request)

Types

type Column

type Column struct {
	Name string `json:"name,omitempty"`

	Type_ string `json:"type,omitempty"`

	Constraints []string `json:"constraints,omitempty"`
}

type OneOfTableAttributesValue

type OneOfTableAttributesValue struct {
}

type Route

type Route struct {
	Name        string
	Method      string
	Pattern     string
	HandlerFunc http.HandlerFunc
}

type Routes

type Routes []Route

type Schema

type Schema struct {
	Columns []Column `json:"columns,omitempty"`

	TableConstraints []string `json:"table_constraints,omitempty"`
}

type Table

type Table struct {
	Name string `json:"name,omitempty"`

	ExternalUrl string `json:"external_url,omitempty"`

	AnimationUrl string `json:"animation_url,omitempty"`

	Image string `json:"image,omitempty"`

	Attributes []TableAttributes `json:"attributes,omitempty"`

	Schema *Schema `json:"schema,omitempty"`
}

type TableAttributes

type TableAttributes struct {
	// The display type for marketplaces
	DisplayType string `json:"display_type,omitempty"`
	// The trait type for marketplaces
	TraitType string `json:"trait_type,omitempty"`
	// The value of the property
	Value interface{} `json:"value,omitempty"`
}

type TransactionReceipt

type TransactionReceipt struct {
	TableId string `json:"table_id,omitempty"`

	TableIds []string `json:"table_ids,omitempty"`

	TransactionHash string `json:"transaction_hash,omitempty"`

	BlockNumber int64 `json:"block_number,omitempty"`

	ChainId int32 `json:"chain_id,omitempty"`

	Error_ string `json:"error,omitempty"`

	ErrorEventIdx int32 `json:"error_event_idx,omitempty"`
}

type VersionInfo

type VersionInfo struct {
	Version int32 `json:"version,omitempty"`

	GitCommit string `json:"git_commit,omitempty"`

	GitBranch string `json:"git_branch,omitempty"`

	GitState string `json:"git_state,omitempty"`

	GitSummary string `json:"git_summary,omitempty"`

	BuildDate string `json:"build_date,omitempty"`

	BinaryVersion string `json:"binary_version,omitempty"`
}