API and data glossary
39 terms you meet when you call a public-data API, each with a plain definition and how Onekey handles it. Every entry links to the docs page that covers it.
A
B
C
Cache hitAn answer served from stored data instead of fetched fresh.Canonical schemaOne fixed set of field names and types that every source is mapped onto.Computed blockValues derived by the API from the fields it returns, kept apart from the source data.Constant-time comparisonComparing two secrets in a way whose duration does not reveal how much matched.CreditThe unit an API bills in; each call costs a published number of them.Cursor paginationPaging through a list by sending back a token from the previous page instead of a page number.
D
E
F
H
I
J
L
M
N
O
P
R
Rate limitA cap on how many requests a caller may make in a period.Reciprocal rank fusion (RRF)A way to merge ranked lists by adding 1/(k + rank) for each list an item appears in.Refund (failed call)Giving credits back when a call does not deliver an answer.Replay windowHow old a signed message may be before it is refused.Request IDA unique identifier for one request, used to trace it.Response envelopeThe fixed outer shape every response has, wrapping the data.Retry-AfterA response header saying how many seconds to wait before trying again.
S
Server-Sent Events (SSE)A one-way HTTP stream where the server pushes named events as they happen.SSRFTricking a server into making requests to addresses it should not reach.Stable and betaWhether an endpoint has been verified against the live source.Stale responseA cached answer older than its fresh window, served now while it refreshes.