Skip to content

Notes

A note is text, Markdown or highlighted code behind its own link. Access, password and expiry work like for files.

Format

formatWhat it is
plainPlain text.
markdownMarkdown with tables and task lists.
codeCode with syntax highlighting; the language is in language.

Highlighting languages:

  • text Text
  • javascript JavaScript
  • typescript TypeScript
  • json JSON
  • python Python
  • bash Bash
  • css CSS
  • xml XML / HTML
  • sql SQL
  • rust Rust
  • go Go
  • c C
  • cpp C++
  • csharp C#
  • yaml YAML

A note holds up to 200,000 characters; its UTF-8 bytes count toward the quota. See POST /pastes for an example.

Edits and revisions

An edit checks the revision so it never overwrites someone else’s changes. Read the text and revision with GET, then send the new text with that revision.

If the note changed meanwhile, the answer is 409 PASTE_REVISION_CONFLICT with currentRevision. Keep your draft, load the current text and resolve the conflict before retrying. An edit keeps the note’s address, password and access.

Code folders

A folder of code is sent as one ZIP: POST /folders. The server decides what stays: folders of dependencies and build output (node_modules, dist, .next, target…), .git, secrets (.env* except .env.example, keys and credentials*), the root .gitignore, non-text and oversized files are not stored — the answer lists them in folder.skipped.

The link page shows the file tree with highlighting and a Download all button: the same ZIP GET /api/media/{id}?download=1 returns.

Methods

Notes · lacuna API