> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/checkout/entry-and-address.md).

# Entry & Address

## Checkout Entry & Address

Start a checkout session and collect delivery information from your customers. These endpoints handle session initialization, delivery address selection, order notes, B2B account settings, and the entry point for external checkout providers.

### Authentication

These endpoints support both authenticated and anonymous sessions.

* **Authenticated users**: Session cookie (`sessionid`) tracks checkout progress.
* **Anonymous users**: Guest checkout is available when the `CAN_GUEST_PURCHASE` setting is enabled.

### Request Format

Include the following header in all checkout requests:

* **x-requested-with**: `XMLHttpRequest`

### Dynamic Settings

#### CAN\_GUEST\_PURCHASE

Controls whether unauthenticated users can proceed through checkout. When disabled, unauthenticated users are redirected to the login page.

#### GIFT\_BOX\_CONFIGURATIONS

Controls whether the gift box option is shown during checkout entry. Set `is_active` to `true` and provide a product `sku` to enable.

#### DEFAULT\_COUNTRY\_CODE

Default country used to pre-populate the country field in the address selection form.

#### REMOTE\_PRICE\_ATTRIBUTE\_KEY

Product attribute key that flags items requiring remote price calculation. When any basket item carries this attribute, the flow redirects to the remote price calculation step after address selection.

#### IDENTITY\_NUMBER\_REQUIRED\_AMOUNT

When set, orders exceeding this total amount require a valid identity number in the shipping address before proceeding.

#### USER\_PHONE\_FORMAT

Display format used as a placeholder for phone number input fields (for example, `05999999999`).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apidocs.akinon.com/commerce-openapis/checkout/entry-and-address.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.