API documentation

Build encrypted secret workflows without sending plaintext to Shhhs.

Your secrets are not read, profiled, trained on, indexed, or retained beyond configured expiry. Support can help with billing cancellation, but cannot restore lost secrets or lost access.

API v1

Team API keys are scoped for encrypted secret creation, request links, request reads, and burn operations.

  • POST /api/v1/secrets
  • POST /api/v1/request-links
  • POST /api/v1/secrets/:id/burn

Zero-knowledge payloads

API v1 rejects plaintext fields and expects ciphertext/envelope data generated by the caller.

  • Scoped API keys
  • No plaintext payloads
  • OpenAPI at /openapi.json

Packages

Free

Anonymous text-only sharing for occasional secrets.

USD 0
  • Text secrets
  • Short TTL
  • View limits
  • No opening codes

10 Secret Bundle

10 secrets / 3 months for paid, occasional work.

USD 29
  • 10 real uses
  • Files
  • Opening codes
  • Request links

7-day Project Pass

A short project window for clients, vendors, and urgent handoffs.

USD 49
  • 7-day access
  • Files
  • Request intake
  • Short TTLs

Pro Monthly

Better value for regular secure sharing.

USD 12/mo
  • 1,000 pushes/month
  • Files
  • Opening codes
  • Console

Team Monthly

Operational controls for teams and API-driven workflows.

USD 49/mo
  • API keys
  • Request intake
  • Policies
  • Multiple admins

FAQ

Does Shhhs process secrets with AI?

No. There is no AI processing on secret content.

Can Shhhs recover a secret?

No. Secret recovery would weaken the privacy model.

What can support recover?

Support can help cancel billing after billing validation, but cannot restore account access or secret content.