For some developers, the existing Data API and Construction API endpoints do not fully support an asset integration. For example, you cannot search for a transaction by hash or access all transactions that affected a particular account. Traditionally, database-intensive functionality was deliberately excluded from the collection of endpoints any Mesh implementation must complete to avoid imposing cumbersome requirements on Mesh implementers (that could require maintaining architecture alongside their core node). Because of the standardization introduced by Mesh, it is possible to write a generic indexer for any Mesh implementation. To avoid a proliferation of interfaces that service Mesh in this layer, we defined a set of standard “indexer” endpoints that let developers automatically integrate (with the SDK they already use to access the Mesh API). Mesh implementations are not required to implement “indexer” endpoints but are welcome to do so! Indexer implementations must proxy non-indexer Data API and Construction API calls to the implementation of interest (potentially caching some data) so that developers do not need to connect to multiple endpoints to access Mesh. All calls contain a NetworkIdentifier so it should be possible to route requests without too much difficulty.

​
Required Endpoints

  • Data API (proxied)
  • Construction API (proxied)
  • /events/*
  • /search/*
If you think an endpoint is missing from this list, please reach out on our Discord.