Assets — list, create, read, update
Manage physical assets tied to a site and account. Reads use project-service GraphQL; creates and updates call fleet-service.
Endpoints
Query parameters (GET /assets)
Create body highlights
- Required:
accountId,siteId,type,manufacturer,model,serialNumber. - Optional:
status,labelIds, dates,description, image file ids,size,expectedLifetime.
PATCH notes
siteIdandaccountIdcannot be changed after creation; PATCH requests that include either field are rejected by request validation with400rather than being silently ignored.- Set
isArchived: trueto archive an asset, orisArchived: falseto unarchive it.
Invoice payments
New: List, get, and create payments on an invoice
You can list payments for an invoice, fetch a single payment by id, and record manual payments. Paths are scoped under the invoice (there is no global /payments resource).
List returns a JSON array, get-by-id returns a single object, and create returns the payment service payload (amounts in dollars on reads; create accepts dollars and converts to cents for core).
Create a payment
Notes
paymentReferenceandnotesare optional.paymentMethodmust be one of:CASH,ACH,CREDIT_CARD,KLARNA,AFFIRM,CHECK.- Core does not expose
GET /payment-records/:id; get-by-id resolves the payment from the invoice’s nested payment records.
