Support
engineering@handbid.com is the right inbox. We read it and we respond — usually same business day for partner integrations.
When you write, include:
- What you were trying to do (one sentence).
- The endpoint(s) involved.
- The response you got (status, body — redact tokens).
- Timestamp in UTC if it’s about a specific request.
- Your integration’s user-agent string or any
x-request-idfrom the response headers.
Status page
Section titled “Status page”Platform-wide incidents are posted at status.handbid.com. Subscribe there for outage notifications scoped to the API, the Socket.IO server, or the manager UI.
Linear (engineering tickets)
Section titled “Linear (engineering tickets)”If your contact at Handbid has shared a Linear ticket reference with you,
the format is HAN-####. We can’t grant external access to Linear, but
referencing the ticket number in email saves us a lookup step.
Roadmap
Section titled “Roadmap”What’s planned for V3 is in active conversation with the partners we already work with. If you’re integrating and want a roadmap call, email above and ask. Specifically useful to mention:
- What’s blocking you today.
- What you’d build if a particular capability existed.
- The size / urgency of your integration.
Security
Section titled “Security”Security disclosures: engineering@handbid.com for now (we don’t have a
dedicated security@ inbox yet). Please mark the subject line
[security] and include reproduction steps.
We don’t run a public bug bounty. Coordinated disclosure is appreciated; we’ll credit reporters who request it.