Auctions and sale mechanics
Expose auction state and transitions programmatically
Create and manage auctions programmatically
Support timed, live, and related sale states
Read bids, lot status, and auction transitions
Developer
Start without building. Extend when you need to.
Most teams use Hammerd out of the box. This page is for when you want more control.
Use APIs, webhooks, and integrations to extend the platform — without rebuilding the core.
- Start with the built-in product
- Launch without custom code or a dev project
- Add integrations when needed
- Use APIs and webhooks for custom flows or internal tools
- Grow without rebuilding
- Extend the system instead of replacing it
Most teams can go live without any upfront engineering work.
Connect only where your existing systems need it.
Scale and add depth without starting from scratch later.
01
Start with the built-in product.
02
Add integrations when needed.
03
Grow without rebuilding.
Optional technical depth
You don’t need this to start
But it’s there when you need deeper control.
Everything behind the product is accessible.
Live docs
Inspect the API surface.
Public docs already cover auctions, listings, orders, payments, fulfilment, and integrations.
API catalog
Review the public linkset.
Hammerd publishes its API catalog under .well-known so the surface is inspectable before a call.
Service description
Check the service metadata.
The public service description names the base API, docs, capabilities, and authentication model.
What you can extend
Plug Hammerd into your existing systems
Use APIs and webhooks to connect auctions to your product, workflows, and data.
Supply and listing workflows
Manage intake, listings, and catalog flow through the same system
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
Buyer and demand data
Access buyer activity and connect it to your own tools
Retrieve buyer signals and audience events
Work with segments, triggers, and launch workflows
Connect demand activity into your own systems
Transactions and trust
Integrate payments, delivery, and post-sale events
Integrate orders, payments, and release checkpoints
Track fulfilment and buyer communication states
Respond to post-sale changes by webhook
Common uses
How teams usually extend Hammerd
Most teams keep their existing product and plug Hammerd into it.
Keep your own front end
Use Hammerd behind your existing UI
Keep your existing product experience while Hammerd runs the auction operations behind it.
Connect your systems
Send auction events into CRM, fulfilment, or internal tools
Use webhooks and APIs to keep existing systems in sync without manual updates.
Add custom logic where needed
Extend workflows without replacing the core
Keep the default product path and add custom logic only where your process needs it.
Start with Hammerd
Start with the product. Extend when you need to.
Most teams don’t need custom work upfront. When you do, everything is already there.
Prefer to talk first? Share your current stack and what you want to connect.