Documentation

Getting started

Conventions

  • All paths below are relative to the base URL. Requests and responses are JSON; send Content-Type: application/json on POST.
  • Ids are UUIDs. Timestamps are ISO 8601 in UTC.
  • Placeholders are addressed by their key, a snake_case name such as client_name that the template endpoint returns beside each label. It derives from the label when the template is first saved and stays put when the label is reworded; the author can change it in the template.
  • Responses carry Cache-Control: no-store and permissive CORS headers, so a browser client works, but a browser is the wrong place for an API token.
  • The API is versioned in the path. Fields may be added to responses without a version change; nothing is removed or renamed within v1.