Authentication
Header
Section titled “Header”Every Public API request must include:
X-API-Key: ska_v1_…_…Do not send the key as a query parameter, in the JSON body, or from browser-side code.
ShishApp issues and manages keys for your subscription (delivery, rotation, revoke). There is no Public API for key self-service. Contact support@shishapp.es for key changes.
Keys may have an expiry date configured by ShishApp. An expired, revoked, or otherwise invalid key yields 401 UNAUTHORIZED with an opaque error — the response does not reveal whether the key existed or why it failed.
Active key limits: Starter 1, Pro 3, Business 10. See Capabilities and plans.
Authorization flow
Section titled “Authorization flow”- Validate the key (format, hash, status, expiry) → otherwise 401
UNAUTHORIZED(opaque; does not reveal whether a key exists or was revoked). - Resolve subscription billing access → if blocked, 402
BILLING_REQUIRED. - Check the capability required by the endpoint → if missing, 403
INSUFFICIENT_CAPABILITY. - Enforce the subscription RPM → if exceeded, 429
RATE_LIMIT_EXCEEDED.
| Status | Code | Meaning |
|---|---|---|
| 401 | UNAUTHORIZED | Missing or invalid API key |
| 402 | BILLING_REQUIRED | Subscription billing blocks access |
| 403 | INSUFFICIENT_CAPABILITY | Plan lacks the required capability |
| 429 | RATE_LIMIT_EXCEEDED | Subscription RPM exceeded |
See Errors and rate limits for headers, grace period, and payload shape.
Using the API implies acceptance of the API Terms and Data license.