***

## title: Making Your First Request

To make your first request to the Rendr API, follow these steps.

<Steps>
  <Step title="Authenticate">
    Before calling any endpoint, obtain an access token using the OAuth2 token endpoint.

    * Use your `client_id` and `client_secret`
    * Tokens are valid for **1 hour**
    * Include the token in the `Authorization: Bearer` header on all requests

    <Tip>
      See [Authentication](https://rendr.docs.buildwithfern.com/documentation/getting-started/authentication) for full details and response formats.
    </Tip>
  </Step>

  <Step title="Create a Delivery">
    Once authenticated, create a delivery. A delivery is the primary orchestration object in Rendr. It contains:

    | Field                          | Description                                 |
    | ------------------------------ | ------------------------------------------- |
    | `store_id` / `store_reference` | The store this delivery originates from     |
    | Customer details               | Recipient name and contact information      |
    | Destination address            | Where the delivery should be sent           |
    | Parcel information             | Dimensions, weight, and item details        |
    | Delivery type                  | Standard, scheduled, regulated, etc.        |
    | Booking controls               | Optional timing and booking behaviour flags |

    When you submit the delivery, Rendr will:

    1. Validate the payload
    2. Apply store configuration
    3. Enforce compliance rules
    4. Assign an initial delivery state

    <Note>
      If immediate booking is enabled, Rendr automatically begins orchestration. No additional calls are required to trigger carrier selection or dispatch.
    </Note>

    For required and optional fields, see the API Reference.
  </Step>

  <Step title="Store the Delivery ID">
    The response will include a unique delivery identifier. You should:

    * **Persist** this ID in your system
    * Use it for **tracking** status and events
    * Use it for **reconciliation** and support queries
  </Step>

  <Step title="Track Progression">
    After creation, Rendr manages the full delivery lifecycle. Poll the delivery object via the API at any time to retrieve the current state.

    <Tip>
      For full lifecycle details, see [Workflow Summary](/documentation/overview/workflow-summary).
    </Tip>
  </Step>
</Steps>