Skip to content
Bullion API

Have a feature request?

Tell us what to build next. A real person reads every request, and we ship from what we hear.

One address, no form, no login: . Replies to any receipt email count too.

Three things that move a request up the list

You do not need to write a spec. A few honest sentences beat a long template.

  • What are you building?

    A sentence or two is enough. The shape of the work matters more than the exact wording.

  • What did you try?

    The endpoint you reached for, the field you wished existed, the workaround you ended up with. Any of these is useful.

  • How much does it matter?

    If it is a one-off, say so. If it would change how you ship, say that too. We use that to prioritise.

How a request becomes a release

No black box. Every step has a name on it.

  1. You send it

    An email, no form, no login. Replies to receipts also count.

  2. We read it

    A real person, usually within a couple of working days. We will reply if you want a reply.

  3. We triage

    Requests go into one of three buckets: shipping soon, on the roadmap, or won’t do. We say which one.

  4. We ship

    Anything that ships lands on this site with a short note on what changed and why.

Reading the request is the easy part

We will tell you which bucket yours is in, and we will not pretend a no is a maybe.