Cessio Docs

Support

Where to write, what to include, and where the source and announcements live

Where to write

You want toWrite to
Report a bug, an error you cannot explain, a stuck settlement, a lost API keysupport@cessio.cc
Talk business — partnerships, listing an instrument, running a maker desk, presshello@cessio.cc
Report a security issuesupport@cessio.cc with [SECURITY] in the subject

We answer as fast as we can, but this is an early-stage project run by a small team — treat response times as best effort, not as an SLA.

Before you write

Most failures have a documented cause and a documented action:

  • Error handling — the full status/code matrix and what a bot should do for each entry.
  • The sign queue — if your quotes or accepts never leave PENDING, this is almost always where the answer is.
  • Settlement tracking — how a trade progresses and what each event means.
  • Quickstart — a working end-to-end run to compare your flow against.

What to include

A report we can act on without a round trip:

  • Network — DevNet, TestNet or MainNet (the switch in the top bar of these docs).
  • Your party hint — never your party id's private key.
  • IdentifiersrfqId, quoteId, tradeId, actionId, and the on-ledger updateId if you have one.
  • The call — method and path, the HTTP status, and the code from the error body.
  • When — a timestamp with its timezone; UTC is easiest.
  • Bodies — request and response, with secrets removed (see below).

Never send us your party private key, your backup key, or your mk_... API key — not in an email, not in a log excerpt, not in a screenshot. We will never ask for them, and anyone who does is not us. If a key has leaked, rotate it (POST /maker/api-key/rotate) before writing.

Source, packages and announcements

On this page