Auditing an integration

Audit one real integration against the failure modes that do not raise errors.

4 of 4 in App builder beginner 10 min

Checked against Graph Horizon (2025-12-11)

Last read 2026-08-30 Due again 2026-11-30

Every protocol claim below was read at these sources on 2026-08-30. Where they disagree with each other, the entry says so.

Audit something real. If you have no integration yet, audit one you are planning.

Audit one integration

  • Name the subgraph you depend on and find who maintains it.
  • Check whether indexers are currently allocated to it, and whether it is indexing healthily.
  • Confirm your API key is not present in any client bundle. Actually search the build output.
  • Add indexing status to your most important query, and decide what the UI shows for behind and for failed.
  • Find every query without a timeout and give it one.
  • Find your highest-volume screen and count the queries it makes per view.
  • Work out queries per user session, and multiply by your expected users.
  • Decide what your application renders when the data source is unavailable, and check that it does that.

Where next

  • Understanding the subgraph you depend on, and maybe writing your own: developer.
  • Why your subgraph is or is not being served: curator.
  • Who serves your queries and what they are dealing with: indexer.
The procedure Official querying guide This site explains why. The official documentation carries the exact steps, flags and config, and it is maintained by the people who ship the code. The numbers Every parameter on one page With the date somebody last read the source, and a note wherever two official pages disagree.