Skip to content

Authentication

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.

  1. Validate the key (format, hash, status, expiry) → otherwise 401 UNAUTHORIZED (opaque; does not reveal whether a key exists or was revoked).
  2. Resolve subscription billing access → if blocked, 402 BILLING_REQUIRED.
  3. Check the capability required by the endpoint → if missing, 403 INSUFFICIENT_CAPABILITY.
  4. Enforce the subscription RPM → if exceeded, 429 RATE_LIMIT_EXCEEDED.
StatusCodeMeaning
401UNAUTHORIZEDMissing or invalid API key
402BILLING_REQUIREDSubscription billing blocks access
403INSUFFICIENT_CAPABILITYPlan lacks the required capability
429RATE_LIMIT_EXCEEDEDSubscription 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.