Skip to main content
All notable changes to the FuelBoss API. For the versioning policy and deprecation timelines, see Versioning.
​
August 20, 2026
Consolidated nomination transaction types.
  • TransactionType now has two values — transfer and cargo — replacing the previous directional values (cargo_in, cargo_out, transfer_in, transfer_out). The direction is now conveyed separately by the new read-only transactionDirection field (in, out, or in_and_out), derived from your company’s role on the nomination.
  • transactionType is now also accepted on nomination upserts (PUT /v1/nominations/supplier, PUT /v1/nominations/receiver) and returned on Get nomination responses together with transactionDirection; previously the field was only available on draft nominations.
  • Breaking change: requests that send a legacy transaction type value are rejected with 422 Unprocessable Entity, and responses return the consolidated values — nominations stored with a legacy value are returned with its consolidated equivalent.
  • Bug fix: deliveryMethod and transactionType on Get draft nominations responses now return the documented lowercase values (e.g. vessel); they previously returned PascalCase.
​
August 19, 2026
Added asset-operator support to nominations.
  • New endpoint Get asset operator companies (GET /v1/asset-operators/companies) returns the companies your company operates assets for (companiesIAmOperatorFor) and the companies you have appointed as your asset operators (myAssetOperators), each with the allowed company entity references.
  • Added optional assetOperatorCompanyIdentifier to the supplier section of nomination upserts (PUT /v1/nominations/supplier) and draft nomination upserts (PUT /v1/nominations/drafts); it is also returned in the supplier section of Get draft nominations responses.
  • Two directions are supported: appoint one of your asset operators on a nomination to grant it view/edit access, or act as the asset operator for a company you operate assets for by setting supplier.companyIdentifier to that company together with an allowed companyEntityReference. See Nominations with an asset operator.
The field is additive and optional — existing integrations are unaffected.
​
August 17, 2026
  • Added optional biofuelQuantityDelivered to conventional bunker delivery notes on the Get operation response. The field is only populated for operations under the RED III operation standard: FuelBoss calculates the biofuel quantity in metric tons from the total delivered quantity, the nomination’s biofuel blend ratio, and the biofuel offset configured by the supplier’s company admin. The field is additive and optional — existing integrations are unaffected.
  • On Create or update draft nomination (PUT /v1/nominations/drafts), the receiver company is now derived from the provided counterpartEntityReference when the receiver companyIdentifier is omitted.
  • Documented the value limits for fuel specification quantities. minQuantity and maxQuantity in nomination and draft nomination quantity ranges must stay within the supported decimal range — at most 28 significant digits, with a maximum magnitude of approximately 7.9 × 10^28 — and values outside that range are rejected with 400 Bad Request.
  • Related platform fix: excessively large quantity values could previously be stored and caused bunkering activities to render incorrectly in the FuelBoss web app schedule; such values are now rejected when a nomination is created or updated.
  • Documentation fix: corrected the conventional bunker delivery note example — measurement units are returned as the stored human-readable strings (e.g. metric tons), not the abbreviated mt previously shown.
​
August 12, 2026
  • Added the Get nominations by client reference endpoint (GET /v1/nominations/{clientReference}/all), which returns every nomination your company can access that shares a given client reference.
  • To support this, Get nomination (GET /v1/nominations/{clientReference}) now returns 422 Unprocessable Entity when more than one accessible nomination shares the requested client reference, instead of arbitrarily returning one of them; the problem detail points to the new endpoint. Single-reference lookups are unaffected.
  • Bug fix: receivers can now read, update, and cancel nominations they created themselves — Get nomination, Create or update nomination (receiver), and Cancel nomination now work for receiver-created nominations.
​
August 4, 2026
Added optional email and phoneNumber fields to the counterpart entity. Both are accepted on the Create or update counterpart entity request (PUT /v1/counterpart-entities) and returned on the Get counterpart entities response. email must be a valid email address (max 320 characters); phoneNumber may contain only digits, spaces, and the characters + - ( ). Both fields are additive and optional — existing integrations are unaffected.
​
August 4, 2026
Added optional companyEntityReference to the receiver section of nomination upserts (PUT /v1/nominations/supplier, PUT /v1/nominations/receiver) and draft nomination upserts (PUT /v1/nominations/drafts), and added optional supplierCompanyEntityReference to the receiver upsert request (PUT /v1/nominations/receiver). These let a company that both supplies and receives the fuel assign its company entities when a receiver creates the nomination. Both are only applied for loading operations where the receiver and supplier are the same company; they are ignored otherwise. The receiver companyEntityReference is also returned on Get nomination and Get draft nominations responses.
​
July 28, 2026
  • Added five new webhook event types: nomination_bunkering_start_time_changed (fires when a nomination’s estimated bunkering start time changes), nomination_bunkering_end_time_changed (fires when the estimated time of completion changes), nomination_contract_changed (fires when the contract assigned to a nomination changes), nomination_company_entity_changed (fires when the supplier company entity changes), and nomination_counterpart_entity_changed (fires when the counterpart entity changes). See the webhook event reference pages for the payload structures.
  • Documentation fix: corrected the documented CloudEvent type for nomination_draft_upserted deliveries to net.fuelboss.nomination.draft.upserted (previously documented as net.fuelboss.nomination_draft.upserted).
​
July 17, 2026
  • All timestamps sent to the API must now include an explicit UTC offset (e.g. +02:00, -04:00, or Z); timestamps without an offset are rejected with 400 Bad Request (see Date and time formats). Applies to all endpoints accepting timestamps: PUT /v1/nominations/supplier, PUT /v1/nominations/receiver, PUT /v1/nominations/drafts, PATCH /v1/nominations/{clientReference}/schedule, and PUT /v1/contracts.
  • Bug fix: the supplied offset is now always honored as an absolute instant — previously, timestamps sent with a zero offset (Z or +00:00) were misinterpreted as local time in the bunkering port and stored shifted.
  • Breaking change: timestamps on Get draft nominations responses are now returned in the local time zone of the bunkering port (with the port’s UTC offset) instead of UTC, matching Get nomination responses, and the fields were renamed to drop the AtUtc suffix: berthTime, pilotTime, estimatedTimeOfBunkering, estimatedTimeOfArrival, estimatedTimeOfDeparture, laycanStart, laycanEnd.
  • Malformed request bodies now return RFC 9457 problem details consistently in all environments.
​
June 23, 2026
Bug fix: the status field on nomination responses (Get nomination, Cancel nomination) now correctly returns supplier_unassigned for nominations that have no supplier assigned. Previously this status was not mapped, which could cause the API to fail when reading such a nomination. Added the supplier_unassigned and amended values to the documented NominationStatus enumeration to match the API contract. Clients performing strict enum validation on status should accept these values.
​
June 15, 2026
  • Made estimatedTimeOfBunkering always required in nomination delivery details (PUT /v1/nominations/supplier and PUT /v1/nominations/receiver). Previously, estimatedTimeOfBunkering could be omitted when laycanStart and laycanEnd were provided. The laycan fields remain fully optional and may be provided together alongside estimatedTimeOfBunkering.
  • Made minQuantity optional within draft nomination quantity ranges — a draft fuel specification can now include a unit without specifying a quantity.
​
June 1, 2026
Added optional gasUpRequired and coolDownRequired boolean fields to delivery details. They indicate whether a gas-up or cool-down operation is required before bunkering (applicable to LNG). The fields are accepted on nomination upserts (supplier and receiver — PUT /v1/nominations/supplier and PUT /v1/nominations/receiver) and draft nomination upserts (PUT /v1/nominations/drafts), and are returned in the corresponding read responses (Get nomination and Get draft nominations).
​
May 25, 2026
  • Added optional priceType field to SupplierDetails on nomination upserts (PUT /v1/nominations/supplier) and to supplier details on draft nomination upserts (PUT /v1/nominations/drafts). The field also appears in nomination and draft nomination read responses. Accepted values are floating and fixed.
  • Added read-only bunkeringLocationName (human-readable name of the bunkering location) to delivery details on Get nomination, Get draft nominations, and Get operation responses.
  • Added read-only estimatedTimeOfCompletion to delivery details on Get nomination responses.
  • Expanded LNG fuel properties (LngFuelProperties) on bunker delivery notes: added methaneNumberMethod, grossHeatingValueMassBtu, netHeatingValueMassBtu, grossHeatingValueVolumeBtuScf, netHeatingValueVolumeBtuScf, grossWobbeIndexBtuScf, and netWobbeIndexBtuScf. The existing MMBtu-suffixed heating-value and Wobbe-index fields are now deprecated in favour of the new Btu/BtuScf variants and retained only for v1 contract compatibility. Formal deprecation effective August 23, 2026 (3-month advance notice per the version lifecycle policy); fields remain in v1 responses, with eventual removal reserved for a future v2 contract.
  • Tightened laycan validation introduced in 1.6.0: laycanStart and laycanEnd must now be supplied together or both omitted — supplying only one is rejected.
​
May 14 and June 11, 2026
  • Added optional laycanStart and laycanEnd fields to DeliveryDetails on nomination upserts (supplier and receiver). estimatedTimeOfBunkering is no longer always required — you may now either supply estimatedTimeOfBunkering alone (the laycan window is derived automatically as [estimatedTimeOfBunkering, estimatedTimeOfBunkering + estimatedBunkeringDurationInMinutes]) or supply laycanStart + laycanEnd directly.
  • Added optional companyName to the receiver section of the supplier upsert request (PUT /v1/nominations/supplier): suppliers can now nominate a receiver by name when the receiving company is not yet known to FuelBoss. If a company with that name already exists, it is reused; otherwise the API automatically registers a company suggestion and uses it as the receiver. companyIdentifier and companyName are mutually exclusive — exactly one must be provided.
  • June 11: deprecated the Reschedule nomination endpoint (PATCH /v1/nominations/{clientReference}/schedule). Use the Create or update nomination endpoints (PUT /v1/nominations/supplier, PUT /v1/nominations/receiver) to reschedule a nomination or change its supplier asset. The endpoint remains functional for backward compatibility but will be removed in a future version.
​
May 12, 2026
  • Added Create or update draft nomination endpoint (PUT /v1/nominations/drafts) and nomination_draft_upserted webhook event.
  • Added operationStandardCode to the Get operation response.
  • Added companyEntityReference to the supplier section of the Get operation response (matches the value used when creating the corresponding nomination).
  • Added transactionType (with the TransactionType enumeration) to draft delivery details — only applicable when the operation standard is of type Transfer.
  • Draft responses now include clientReference, supplier companyEntityReference, and receiver counterpartEntityReference/companyName/vesselName.
  • Breaking change (previously coordinated with consumers): the API now identifies a company entity by its reference — the value you set in the FuelBoss Entity Management module and can mirror to your ERP — rather than an internal identifier that was not surfaced in the FuelBoss web app. As a result, the field on GET /v1/company-entities responses changed from identifier to reference, and the supplier section of both firm nominations (GET /v1/nominations/{clientReference}) and drafts changed from companyEntityIdentifier to companyEntityReference.
  • Bug fix: the GET /v1/operations/{clientReference} response now returns status in lowercase (e.g. "ended") matching the documented OperationStatus enum values and Swagger schema; it previously returned PascalCase.
  • Added validation that the receiver counterpartEntityReference must belong to the receiver company.
​
April 12, 2026
  • Added multiple new endpoints for getting draft nominations, creating or updating contracts, getting contracts, getting company entities, getting counterpart entities, and creating or updating counterpart entities.
  • Added companyEntityIdentifier to SupplierDetails and counterpartEntityReference to ReceiverDetails.
  • Bug fixes: added mmbtu and mwh fuel measurement units, added productName to LNG bunker delivery notes, and fixed delivery method casing.
​
March 10, 2026
  • Added Accept nomination endpoint (PUT /v1/nominations/{clientReference}/accept).
  • Improved error response handling with RFC 9457 compliant Problem Details — error responses no longer expose internal implementation details.
​
February 18, 2026
  • Added optional custom headers support for webhook subscriptions. Custom headers are sent with every webhook delivery, enabling integration with API gateways like Azure API Management.
  • Added headerKeys field to webhook subscription responses.
  • Added webhook delivery source IP addresses for firewall allowlisting.
​
February 10, 2026
  • Added Create or update nomination (receiver) endpoint. The receiver endpoint uses dedicated ReceiverDetails without companyIdentifier.
  • Added Cancel nomination endpoint (PUT) with mandatory reason.
  • Added accepted nomination status.
  • Added status field to the Get nomination response.
​
January 2, 2026
Added nomination_created webhook event. Added biofuel properties to fuel specification with the BiofuelGenerationCode enumeration.
​
December 22, 2025
Production release. Changed the reschedule nomination endpoint to use clientReference as path parameter.
​
December 1, 2025
Production release candidate #2 with various changes to contracts, including vessel/asset identifier, bunker delivery note, and how measurement units are represented.
​
October 31, 2025
Production release candidate #1 with nominations, operations, webhooks, and common resources.