> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/order-integration-b2c.md).

# Order Integration B2C

#### Description

The order endpoint should be a REST API delivering order and product data. Claimlane will call this endpoint when a customer is creating a ticket. The endpoint should accept two values, for example email and order number.

All data provided by this endpoint will be carried through Claimlane and can be used by later API's for example for refunds, shipping etc.

Claimlane supports a standard order integration data model that can be found here:

<https://server-claimlane.claimlane.com/api-docs/#/callbacks/b2c-order-integration>

You can also follow a different data model if that is easier for you in which case we will have to build a mapper on our side.

Examples of other data models can be found below.

Example Endpoint:

```javascript
GET https://api.claimlane.com/order?orderNumber={ORDER_NUMBER}&email={EMAIL}
```

Example data model 1:

```javascript
{
	order: {
    // Order info
	  orderDate: string;
    deliveryDate: string;
    orderNumber: string;
    invoiceNumber: string;
    customerNumber: string;
    customerEmail: string;

		// Address and delivery
    billingAddressName: string;
    billingAddressPhoneNumber: string;
    billingAddress: string;
    billingAddressZipCode: string;
    billingAddressCity: string;
    billingAddressCountry: string;
    billingAddressCvrNo: string;
    billingAddressAtt: string;
    deliveryAddressName: string;
    deliveryAddress: string;
    deliveryAddressCity: string;
    deliveryAddressZipCode: string;
    deliveryAddressPhoneNumber: string;
    deliveryAddressCountry: string;
    shippingWeight: number;
  },
	products: [{
    // Product info
    productId: string; // REQUIRED
    productName: string; // REQUIRED
    productUnitPrice: number;
    productQuantity: number;
    productDescription: string;
    productCategory: string;
    productSku: string;
    productUrl: string;
    productEan: string;
    productImageUrl: string;
    productDeliveryTime: string;

    // Supplier information
    supplierName: string;
    supplierNumber: string;
    supplierSku: string;
	}]
}
```

Example data model 2:

```javascript
{
	products: [{
    // Order info
	  orderDate: string;
    deliveryDate: string;
    orderNumber: string;
    invoiceNumber: string;
    customerNumber: string;
    customerEmail: string;

    // Address and delivery
    billingAddressName: string;
    billingAddressPhoneNumber: string;
    billingAddress: string;
    billingAddressZipCode: string;
    billingAddressCity: string;
    billingAddressCountry: string;
    billingAddressCvrNo: string;
    billingAddressAtt: string;
    deliveryAddressName: string;
    deliveryAddress: string;
    deliveryAddressCity: string;
    deliveryAddressZipCode: string;
    deliveryAddressPhoneNumber: string;
    deliveryAddressCountry: string;
    shippingWeight: number;

    // Product info
    productId: string; // REQUIRED
    productName: string; // REQUIRED
    productUnitPrice: number;
    productQuantity: number;
    productDescription: string;
    productCategory: string;
    productSku: string;
    productUrl: string;
    productEan: string;
    productImageUrl: string;
    productDeliveryTime: string;

    // Supplier information
    supplierName: string;
    supplierNumber: string;
    supplierSku: string;
	}]
}
```


---

# 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://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/order-integration-b2c.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.