Skip to content
xashadocs
IntroductionGetting startedQuickstartGetting startedEncryptionGetting startedSharing linksGetting startedCreate a secretAPI referenceConsume a secretAPI referenceDelete a secretAPI referenceHealthAPI referenceReadinessAPI referenceOpenAPI specificationAPI referenceErrors and limitsGuides
Tab to a result · Enter to open · Esc to close
QuickstartGitHub ↗
Documentation

Getting started

Introduction

Share private text with one-time retrieval. Encrypt locally, send a link, and let the recipient reveal it once.

How it works#

Your app encrypts text before sending it to Xasha. The service stores the encrypted envelope and returns a reference. The encryption key stays with the sender, then travels in the share link’s URL fragment.

When the recipient chooses Reveal, Xasha returns the envelope and consumes the secret in one operation. Your app decrypts it locally.

Start here#

Follow the quickstart for a complete integration, or jump to the API reference.

QuickstartCreate, share, reveal, and delete.
EncryptionA complete Web Crypto helper.
Errors and limitsResponse codes and safe failure handling.

Base URL#

text
https://api.xasha.site

No account, API key, or SDK is required. Secret routes accept public browser requests without cookies. Use HTTPS and credentials: 'omit'.

Privacy by default#

Keep secret text, keys, complete links, and deletion tokens out of logs, analytics, and browser storage. Never send plaintext or encryption keys to the API.

Anyone with a complete share link can retrieve the secret. Browser encryption does not prevent a service that supplies the browser code from changing that code.