> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ofiniti.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nominations

> Create, update and retrieve nominations and draft nominations, including nominations with an asset operator.

Nominations represent requests for bunkering operations. You identify a nomination by its `clientReference` — your unique identifier, at most 100 characters, alphanumeric and hyphens only (`a-z`, `A-Z`, `0-9`, `-`) — and the create-or-update endpoints are idempotent on it. All timestamps you send must include an explicit UTC offset — see [Date and time formats](/fuelboss/api-integration-guide/conventions#date-and-time-formats).

Create and update nominations through the endpoint matching your role: [as a supplier](/api-reference/nominations/creates-or-updates-a-nomination-as-a-supplier) (`PUT /v1/nominations/supplier`) or [as a receiver](/api-reference/nominations/creates-or-updates-a-nomination-as-a-receiver) (`PUT /v1/nominations/receiver`). As a receiver, your authenticated company is used as the receiver — the receiver section has no `companyIdentifier` — and you identify the supplier with `supplierCompanyIdentifier`; `supplierCompanyEntityReference` is only applied for loading or transfer operations where the receiver and supplier are the same company and is ignored otherwise. Field-level semantics for every request and response body are documented on the corresponding API reference page.

Draft nominations are lightweight, in-progress nominations: when [creating or updating a draft](/api-reference/nominations/creates-or-updates-a-draft-nomination) (`PUT /v1/nominations/drafts`), only `operationStandardCode`, `laycanStart`, and `laycanEnd` are mandatory, and everything else can be filled in later through subsequent upserts or directly in the FuelBoss web app. [Retrieving drafts](/api-reference/nominations/retrieves-draft-nominations) (`GET /v1/nominations/drafts`) is paginated with an opaque cursor (`cursor` and `limit` query parameters; default 50, maximum 200 per page).

<Warning>
  `PATCH /v1/nominations/{clientReference}/schedule` ([reschedule](/api-reference/nominations/reschedules-an-existing-nomination-deprecated)) is deprecated. Use the create-or-update endpoints to change scheduling information instead: `delivery.estimatedTimeOfBunkering` and `delivery.estimatedBunkeringDurationInMinutes` cover rescheduling, and `supplier.assetIdentifier` covers supplier asset changes. The endpoint remains functional for backward compatibility but will be removed in a future version.
</Warning>

## Nominations with an asset operator

An **asset operator** is a company that manages bunkering assets (vessels or terminals) on behalf of another company. FuelBoss lets these relationships be modelled on a nomination so the operator can work on it. Use [Get Asset Operator Companies](/api-reference/common/retrieves-asset-operator-relationships-and-their-allowed-entities) to discover which relationships exist for your company and which company entities each relationship allows.

There are two directions, both driven by the supplier section of the [Create or Update Nomination (Supplier)](/api-reference/nominations/creates-or-updates-a-nomination-as-a-supplier) (`PUT /v1/nominations/supplier`) and [Create or Update Draft Nomination](/api-reference/nominations/creates-or-updates-a-draft-nomination) (`PUT /v1/nominations/drafts`) requests:

**1. You are the supplier and appoint an asset operator.** You create the nomination for your own company (leave `supplier.companyIdentifier` empty, or set it to your own company) and set `supplier.assetOperatorCompanyIdentifier` to a company you have appointed as your asset operator. That company then gains the ability to view and edit the nomination. The appointed company must appear in the `myAssetOperators` list returned by [Get Asset Operator Companies](/api-reference/common/retrieves-asset-operator-relationships-and-their-allowed-entities). If you also provide `supplier.companyEntityReference`, it must be one of the entities that relationship allows.

```json theme={null}
{
  "supplier": {
    "companyIdentifier": "COMP-123",
    "assetOperatorCompanyIdentifier": "COMP-OPERATOR-1",
    "companyEntityReference": "ENT-SUPPLIER-01"
  }
}
```

**2. You act as the asset operator for another company.** You create the nomination on behalf of a company you operate assets for by setting `supplier.companyIdentifier` to that company and providing a `supplier.companyEntityReference` that the relationship allows. The supplier company you name must appear in the `companiesIAmOperatorFor` list returned by [Get Asset Operator Companies](/api-reference/common/retrieves-asset-operator-relationships-and-their-allowed-entities), and the `companyEntityReference` is **required** and must be one of that company's allowed entity references. Your own company is recorded as the asset operator; if you also send `assetOperatorCompanyIdentifier`, it must equal your own company identifier.

```json theme={null}
{
  "supplier": {
    "companyIdentifier": "COMP-SUPPLIER-2",
    "companyEntityReference": "ENT-ALLOWED-07"
  }
}
```

When a supplier company, asset operator company, or company entity reference cannot be resolved to an allowed relationship, the request is rejected with `422 Unprocessable Entity`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.