Skip to main content
POST
/
v1
/
orders
Create an order (activate a listing)
curl --request POST \
  --url https://api.zeroclick.quest/v1/orders \
  --header 'Content-Type: application/json' \
  --header 'x-zam-api-key: <api-key>' \
  --data '
{
  "listingId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "requestBody": {}
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "userId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "listingId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "orderState": "pending",
  "requestBody": {},
  "result": {},
  "errorMessage": "<string>",
  "startedAt": "2023-11-07T05:31:56Z",
  "completedAt": "2023-11-07T05:31:56Z",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "2023-11-07T05:31:56Z"
}

Authorizations

​
x-zam-api-key
string
header
required

ZAM API key. Starts with zam_.

Body

application/json
​
listingId
string<uuid>
required

ID of the published listing to activate

​
requestBody
object

Input data validated against the listing's inputSchema

Response

Created order (may be pending, running, completed, or failed depending on execution speed)

​
id
string<uuid>
​
userId
string<uuid>
​
listingId
string<uuid>
​
orderState
enum<string>
Available options:
pending,
running,
completed,
failed
​
requestBody
object

The input sent to the listing's endpoint

​
result
object

The response from the listing's endpoint (when completed)

​
errorMessage
string | null

Error details (when failed)

​
startedAt
string<date-time> | null
​
completedAt
string<date-time> | null
​
createdAt
string<date-time>
​
updatedAt
string<date-time>