Skip to content

by Startups.Studio

Order.fulfill

POST /{namespace}/orders/{order}/fulfill

Fulfill grants what an Order bought: Entitlements for software and data, a shipment for goods.

Noun: Order
Mode: do
Event: Order.fulfilled

You, to your agent

Fulfill the latest order.

curl -X POST https://api.sb/tutorloop.com/orders/order_1/fulfill \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

import { $ } from 'startup-builder'

const order = await $.Order.fulfill({ order: 'order_1' })

npx startup-builder do Order.fulfill --json '{"order":"order_1"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Order.fulfill({ order: 'order_1' })"
  }
}

Inputs

Input	Type	Required	Description
`order`	Order	required	The paid Order.

Outputs

Output	Type	Required	Description
`order`	Order	required	The fulfilled Order.

Effects

Emits Order.fulfilled.
Performed by the Delivery Manager.
Two-way: it runs at once, in the try, send and do modes.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Order.fulfill
The record is not in a state that allows this Verb, so the call is refused.	`refused`	Read the record, run the Verb that moves it to an allowed state, then retry.	Order.fulfill

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Order.dispute

Previous Page

Order.get

Next Page