AkousaX-API-Version Header
All v1 responses now include the X-API-Version: 1.0.0 header. Clients can use this header to verify which API version served the response and to implement version-aware logic in their integrations.
A chronological log of changes, improvements, and new features in the akousa.net Developer API.
All v1 responses now include the X-API-Version: 1.0.0 header. Clients can use this header to verify which API version served the response and to implement version-aware logic in their integrations.
Endpoints can now signal deprecation via RFC 8594-compliant Deprecation, Sunset, and Link headers. When an endpoint is scheduled for removal, the Deprecation header indicates the deprecation date, the Sunset header signals the removal date, and the Link header points to the replacement endpoint documentation.
All error responses now return a consistent { ok: false, error, code?, status } shape. The legacy { error } shape is deprecated and will be removed in a future version. Success responses continue to return { ok: true, data, ... }. This unification simplifies client-side error handling across all 78 endpoints.
Launched the akousa.net Developer API with 78 endpoints across 16 groups, a complete OpenAPI 3.1 specification, 3-tier pricing (Starter, Plus, Pro), API key authentication using the ak_ prefix, and Redis-backed rate limiting with per-tier daily quotas. Interactive documentation with code examples in 8 languages (cURL, JavaScript, Python, Go, PHP, Ruby, Java, C#).