kwery uses API keys scoped to your organization. Keys can be rotated and scoped per environment so staging and production never share credentials. API documentation.
Limits depend on your plan and source. Direct API plans are sized to your real traffic profile during onboarding; self-serve access uses published per-tier limits. There is no hard cap on job size — submit 1,000 GTINs or 10 million, and results stream back as batches complete. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers, so you can back off gracefully by reading them instead of modelling your own quota separately.
Each resource has a semantic version. Additive changes ship without a bump; renames and removals ship as a new major version pinned via header. Old clients keep working; upgrading is opt-in.
Node / TypeScript is the primary SDK. Python is in beta. Any HTTP client works against the REST endpoints directly — the docs include cURL examples for every route. API documentation.
Request API access and the team will walk through sources, volumes, and integration in detail.