List Ipas
Authorizations
JWT issued by Dynamic Labs or Privy. Sent in the x-juno-jwt header on every authenticated request.
Headers
Tenant org ID for multi-tenant auth
Controls how timestamp fields are serialized in JSON response bodies.
Default (header omitted or any other value): epoch milliseconds as integers.
iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.
Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".
Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.
Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.
"iso8601"
Query Parameters
How far an errand has got.
While an agent is working out what to buy it reads as qualifying, searching or
validating. It then waits for the user: pending_clarification needs a question
answered, pending_approval needs the purchase approved. Once approved it may
sit in monitoring until the conditions it was given are met, and reads as
executing while the purchase is being made.
completed, failed, expired and cancelled are final. An errand in one of
those four states will not change again, and can no longer be clarified or
cancelled.
What may be done to an errand follows from where it has got to. Cancelling works
in any of the eight states that are not final. Answering questions works only
while the errand is actually waiting on some — qualifying or
pending_clarification — and is refused everywhere else, so its state is worth
reading before trying.
qualifying, searching, validating, pending_approval, pending_clarification, approved, monitoring, executing, completed, failed, expired, cancelled What kind of purchase an errand is for.
product is physical or digital goods. service covers bookings such as flights,
hotels or reservations. composite is a purchase made of several parts bought
together, such as a trip.
product, service, composite created_at, -created_at, updated_at, -updated_at, status, -status x >= 01 <= x <= 100Expand related resources. Options: originating_agent_task, executing_agent_task, candidates, manifests, events