// product feedback

Have a feature request?

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

// email us

One address, no form, no login.

Drop a line at hello@bullionapi.dev. Replies to any receipt email count too.

// what helps us act on it

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.

// use case

What are you building?

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

// today

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.

// scale

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.

// what happens next

How a request becomes a release.

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

01

You send it

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

02

We read it

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

03

We triage

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

04

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.