market
Before you integrate
Two obligations on your client, so that we can add fields and values without breaking you. Both are conditions of the compatibility promise below, not suggestions:
- Ignore response fields you do not recognise. We add fields without changing the API version. Deserialize non-strictly — a client that rejects unknown keys will break on our next additive release.
- Tolerate values you do not recognise in any string-typed enumeration, now or later.
Do not
switchon one without a default branch.
What we will change, and how you will hear about it:
| Additive changes — new fields, new optional parameters, new accepted values | Ship without notice and without a version bump. Covered by the two obligations above. |
| Rate limiting | Live. Requests are limited per minute against your account's ceiling; going over answers 429 plus Retry-After. See Rate limiting. Build your client so that a 429 backs off rather than retries in a tight loop. |
| Breaking changes — a field removed, renamed, retyped, or validation made stricter | Never silently. You get notice and an overlap period. |