Skip to main content
POST
Apply a cost kit to a cost sheet

Authorizations

X-Session-Token
string
header
required

Session token for authentication.

Path Parameters

cost_kit_id
string<uuid>
required

The unique identifier for the cost kit.

Body

application/vnd.api+json

Where to apply the kit, how much of it, and as at what date.

The request type is cost-kit-applications, but there is no such resource: nothing of that name is stored and nothing can be fetched back by that id. It names the action, and the response is the collection of cost lines the action produced. The id that groups those lines travels on the lines themselves as cost_kit_application_id.

data
object
required

Response

The cost lines the kit produced — one per item in force on the work date, each priced and frozen exactly as a hand-entered line is.

They all share a cost_kit_application_id and carry the same cost_kit snapshot, so a client can render and remove them as the single action they were.

JSON API response object

data
The cost lines written by applying the kit · object[]
required
meta
object
required
jsonapi
object
required
included
object[]

Related resources that can be included when a cost line is returned.

cost-items and cost-item-versions are both optional on a line, so asking for either simply yields nothing for the lines that have none — an ad-hoc line has no rate code, and a line priced on the job has no register version behind its rate. Neither is an error, and a request for both across a mixed collection comes back with whatever exists.

An organisation