Maintenance

Create a service record

Two-step operator-confirmed write for non-mobile clients. First send the proposed record with an 8-128 character Idempotency-Key; Fleetkeep returns confirmation_required. Retry the identical body and key with X-Fleetkeep-Confirmation. Safe retries return the original record with replay true. The signed Fleetkeep mobile client uses its native review flow. updateServiceReminder defaults to true.

post/api/v1/vehicles/{id}/service-records

Request

  • Base URL: https://fleetkeep.co.uk
  • URL: https://fleetkeep.co.uk/api/v1/vehicles/{id}/service-records
  • Auth: OAuth 2 (authorization code, authorization URL https://fleetkeep.co.uk/auth/oauth2/authorize, token URL https://fleetkeep.co.uk/auth/oauth2/token, scopes: maintenance:write)

Headers

Idempotency-Keystring required
X-Fleetkeep-Confirmationstring

Five-minute confirmation token returned by the initial 409 response and bound to this exact record version and bearer-token JTI.

Request body

servicedAtstring date required
odometerMileageinteger nullable
supplierstring nullable
invoiceReferencestring nullable
costPenceinteger nullable
workSummarystring required
partsNotesstring nullable
nextServiceDueDatestring date nullable
nextServiceDueMileageinteger nullable
notesstring nullable
updateServiceReminderboolean

Response

An idempotent retry returned the previously created record.

replayboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.