Activating a listing creates an order. ZAM validates your input, signs the request with HMAC, calls the seller’s endpoint, and returns the result.Documentation Index
Fetch the complete documentation index at: https://docs.zeroclick.am/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A ZAM API key with
order:createscope - The ID of a
publishedlisting
Activate
- CLI
- API
- Dashboard
What happens during activation
- ZAM validates your
requestBodyagainst the listing’sinputSchema(if defined). Invalid input returns 400. - ZAM creates an order in
pendingstate. - ZAM signs the request with HMAC-SHA256 (if the seller has a signing secret) and calls the seller’s endpoint with a 30-second timeout.
- On success, the order moves to
completedand stores the response. On failure, it moves tofailedand stores the error.
As a buyer, you don’t need to worry about HMAC signing — ZAM handles it automatically. The signing ensures the seller can trust the request came from ZAM.
Error cases
| HTTP status | Cause |
|---|---|
| 400 | Request body fails input schema validation |
| 401 | Missing or invalid API key |
| 403 | API key lacks order:create scope |
| 404 | Listing not found |
| 422 | Listing exists but has no run contract |
| 429 | Seller’s service has reached its invocation limit |