Lists sales order status changes in a fixed order, newest first (changes at the same instant by `id`, descending); Sort is ignored. One row per change: the status the sales order moved into, the status it left, who made the change and when, and the sales order's number, customer, salesperson, current status and part line count. Revision and deletion events, and every change of a deleted sales order, are left out.
Changed onRequest
- Base URLhttps://api.fulcrumpro.com
- URLhttps://api.fulcrumpro.com/api/sales-orders/status-history/list
- Authnone declared
Query parameters
Sort field
Specify sorting direction.
Sort direction
Number of records to skip. Defaults to 0. Combine with FulcrumProduct.PublicApi.Dto.Common.PagingDto.Take to page through a result set larger than one page.
Number of records to return. Validation accepts 0 through 5000, but 0 is not a page size and what an endpoint does with it varies, so send a value from 1 to 5000.
Two cases differ. A request that supplies paging but leaves this field out takes this field's default of <b>50</b>. A request that supplies no paging at all is endpoint-specific — some define their own fallback — so it does not reliably mean any particular number of records. Either way the response says nothing about records it did not return, so send this explicitly whenever the size of the answer matters. Endpoints returning a paged envelope report totalCount and hasNextPage alongside the records; endpoints returning a bare array report neither, so page those with FulcrumProduct.PublicApi.Dto.Common.PagingDto.Skip until a page comes back shorter than the value requested.
Request body
Response
A page of status changes with the total matching count.
Changes
- info
endpoint added
- info