Kasify API - Kasify

Versioning

All business endpoints are served under a /v1 prefix (e.g. GET /v1/properties). The OpenAPI spec at /openapi.json sits outside the version prefix because it describes the API rather than serves business data. Within v1 only additive, backwards-compatible changes ship; breaking changes land at /v2.

Rate limiting

Every endpoint is subject to rate limiting. When a bucket is exhausted the API responds with HTTP 429 Too Many Requests, a Retry-After header (seconds), and the standard error envelope:


Code
{ "code": "rate_limit.exceeded", "message": "Too many requests. Retry after 42 seconds." }

Default buckets (1-minute rolling window): 100/min per personal access token, 50/min per IP on /v1/geo/..., and 10/min per IP on the OpenAPI spec. See the Getting Started page for details.

Versioning

Rate limiting

Every endpoint is subject to rate limiting. When a bucket is exhausted the API responds with HTTP 429 Too Many Requests, a Retry-After header (seconds), and the standard error envelope:


Code
{ "code": "rate_limit.exceeded", "message": "Too many requests. Retry after 42 seconds." }

Default buckets (1-minute rolling window): 100/min per personal access token, 50/min per IP on /v1/geo/..., and 10/min per IP on the OpenAPI spec. See the Getting Started page for details.