> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/booking-engine-guide/booking-engine-widget/use-cases/testing-in-demo-environment.md).

# Testing in the Demo environment

The Booking Engine Widget uses the Production environment by default. Before you are ready to run the Booking Engine Widget against real data, you should use the Booking Engine Widget with [Demo environment](/booking-engine-guide/booking-engine-api/guidelines/environments.md) data instead. Most of the steps are the same as those described in the [Getting started](/booking-engine-guide/booking-engine-widget/getting-started.md) section. The only difference is in [Step 2: Initialize Booking Engine Widget](/booking-engine-guide/booking-engine-widget/getting-started.md#step-2-initialize-booking-engine-widget).

In comparison to the default example, you can set an optional [`dataBaseUrl`](/booking-engine-guide/booking-engine-widget/reference.md#string-databaseurl) property to point to the Demo environment:

```javascript
Mews.Distributor(
    { configurationIds: ['aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee'] },
    function (api) {
        api.open();
    },
    { dataBaseUrl: 'https://api.mews-demo.com' }
);
```

> **Important:** Make sure you use `Configuration IDs` from the correct environment, otherwise they will not be used - see [Why doesn't the Booking Engine use the Configuration IDs I've provided?](/booking-engine-guide/faq.md#why-doesnt-the-booking-engine-use-the-configuration-ids-ive-provided).

After making this change, the Booking Engine Widget will start using data from the [Demo environment](/booking-engine-guide/booking-engine-api/guidelines/environments.md#demo-environment) instead of from the [Production environment](/booking-engine-guide/booking-engine-api/guidelines/environments.md#production-environment).


---

# 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://docs.mews.com/booking-engine-guide/booking-engine-widget/use-cases/testing-in-demo-environment.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.