SATIK DEVELOPER DOCS · V1 BETA
Use a full check where it counts.
Normalize early. Verify before dispatch.
Normalize at checkout
Use /addresses/normalize to clean and parse input without a Google call. Normalization does not claim that an address exists and does not return a verdict.
Repeat requests
Choose the right kind of repeat request. Never share Google content across tenants.
| Request type | Quota behavior |
|---|---|
| Eligible cached match | Exact normalized matches are cached within a tenant for a fixed maximum window. Cache hits cost fewer units. |
| Idempotent retry | Retries of the same request with its idempotency key do not consume additional quota. |
Learn how to retry safely
See the idempotency guide for a complete cURL example, key lifecycle, conflict handling, and the difference between retry protection and address caching.
| Guide | What it covers |
|---|---|
| Idempotency keys | Send an optional key, reuse it for retries, and understand verification IDs and cached results. |