7 docs tagged with "API design"

Rule: an API is not an endpoint, it is a promise you cannot withdraw. Internal code can be

Rule: an API manages the lifecycle of resources; it does not expose your actions or your tables.

Rule: when the answer does not exist yet, do not pretend the request can return it. Model the

Rule: a list endpoint is a cost-control mechanism first and a feature second. Unbounded

Rule: without a limit, one client's mistake becomes everyone's outage. A rate limit is not

Rule: sending a webhook once is not delivering it. Without signatures, retries, and a way to

Reference API designs from Binance and HashKey WebSocket endpoints.