Skip to main content
Tuck’s ingest API is intentionally small. It accepts text and routing metadata, then lets an unlocked Tuck device pull the item into the encrypted vault.

Endpoint

Send a request to the ingest service’s /v1/messages endpoint with your ingest token.

What the API is for

Use it for lightweight automations that need to capture text into Tuck. It is not a general-purpose API for reading or editing the rest of an unlocked vault.

Attachments

The ingest API is text-only in the current architecture. Attachment bytes need to be encrypted on a Tuck client.