#api
5 approved public terms with this tag.
Webhook
机器辅助翻译草稿 (Chinese) for "Webhook": A user-defined HTTP callback that fires automatically when a specific event occurs in a source system. Rather than polling an API repeatedly, webhooks push data to a listener URL the moment something happens — making integrations real-time and efficient.
“示例草稿: We set up a webhook so Slack gets notified instantly every time a new definition is published.”
Idempotency
机器辅助翻译草稿 (Chinese) for "Idempotency": The property of an operation where performing it multiple times produces the same result as performing it once. Idempotent API endpoints are critical for safe retries — if a network error occurs, the client can re-send the request without fear of duplicating side effects like charges or database records.
“示例草稿: Pass an idempotency key with payment requests so retries don't charge the customer twice.”
Rate Limiting
机器辅助翻译草稿 (Chinese) for "Rate Limiting": A technique for controlling the frequency of requests a client can make to an API or service within a given time window. Rate limiting protects systems from abuse, prevents overload, and ensures fair resource allocation among consumers. Responses typically include headers indicating current usage and remaining quota.
“示例草稿: The API returned a 429 Too Many Requests error once rate limiting kicked in at 100 calls per minute.”
API-First
机器辅助翻译草稿 (Chinese) for "API-First": A design philosophy where the API contract is defined and agreed upon before any implementation begins. API-first teams treat the API as the product — writing the specification first (e.g., in OpenAPI), getting feedback from consumers, then building both client and server simultaneously against the agreed contract.
“示例草稿: Their API-first approach meant the mobile app team could start building against the spec before the backend was done.”
机器辅助翻译草稿 (Chinese) for "Graph API": An API that exposes data as a graph of interconnected nodes and edges, allowing clients to traverse relationships and fetch exactly the data they need in a single request. GraphQL is the most common implementation, replacing multiple REST endpoints with a flexible query language.
“示例草稿: The graph API let the client fetch a user, their posts, and each post's comments in one request instead of four.”