Developers
You don’t need custom code to launch — most teams run on the built-in product. When you want more control, APIs and webhooks connect Hammerd to the systems you already use.
Integration map. Your branded storefront sends bids and buyer sign-in to Hammerd, and Hammerd serves catalog, listings, and auctions back to it. Hammerd sends webhook events about orders, payments, and delivery to your systems, such as a CRM or fulfilment tool, and those systems make API calls back to Hammerd for listings, orders, and shipping.
Your branded storefront
Hammerd’s built-in storefront, or your own front end.
Hammerd
Auctions, orders, payments, and delivery on one record.
Your systems
CRM, fulfilment, and internal tools.
Two ways to use Hammerd
Everything on the left works on day one. The right is what your developers add, only where your process needs it.
Path 1 · No code
What Hammerd already does for you.
Path 2 · APIs and webhooks
What your developers can build on top.
Create and manage auctions programmatically
Support timed, live, and related sale states
Read bids, lot status, and auction transitions
Manage lots, consignments, and listing drafts
Track consignment and valuation pipeline stages
Track handoff states from intake to publish
Structure sale configuration around inventory groups
Retrieve buyer signals and audience events
Work with segments, triggers, and launch workflows
Connect demand activity into your own systems
Integrate orders, payments, and release checkpoints
Track fulfilment and buyer communication states
Respond to post-sale changes by webhook
Illustrative example
Hammerd runs the sale and the payment. A webhook hands the order to your own tools.
Built into Hammerd
The winning bid on your storefront creates an order in Hammerd.
Built into Hammerd
Checkout and payment happen inside Hammerd. Nothing for you to build.
Your integration
Your endpoint is notified that the order has changed.
Your integration
Your service reads the order through the API, then books the shipment or updates the customer in your CRM.
This is an example, not a spec — exact webhook events and payloads are in the API docs. API calls authenticate with a bearer API key or user access token, plus a tenant header on shared hosts.
Authorization: Bearer <API key or user access token>
X-Tenant-ID: <your tenant>Technical resources
All public and inspectable before a conversation.
Most teams don’t need custom work upfront. When you do, the APIs are already there.
Prefer to talk first?
Share your current stack and what you want to connect.
We’ll reply by email.