# Getting started

This page walks you through the key steps to begin developing your integration with the **Mews Connector API**. Whether you're exploring the demo environment, preparing for certification, or validating your first request, this guide covers the tools, environments and concepts you'll need.

{% hint style="info" %}

#### Ready to try a test call?

Jump to [Step 2: Make your first API call](#make-your-first-api-call).
{% endhint %}

## What you’ll need

Before making your first request, make sure you're familiar with the following:

* **Authentication tokens**\
  Every API request requires:
  * `ClientToken`: Identifies your application. Issued by Mews.
  * `AccessToken`: Identifies the enterprise or property you're connecting to. Issued by the property.
  * `Client`: A short string naming your application.
* **Mews environments**\
  Mews provides two environments:
  * [Demo environment](/connector-api/guidelines/environments.md#demo-environment) – for development and testing.
    * Net pricing and Gross pricing variants simulate different tax regimes used by properties in different jurisdictions.
  * [Production environment](/connector-api/guidelines/environments.md#production-environment) – used by live properties after certification.
* **Mews Operations**\
  You can optionally log into the UI of Mews Operations (used by hotel staff) to understand how API data maps to the product.
* **Demo credentials**\
  Mews provides shared tokens and login details for test properties. These are suitable for early development, but subject to [rate limits](/connector-api/guidelines/requests.md#request-limits).

{% hint style="info" %}

#### Want to know more?

For full details, see [Authentication](/connector-api/guidelines/authentication.md) and [Environments](/connector-api/guidelines/environments.md).
{% endhint %}

{% stepper %}
{% step %}

### Set up your environment

To begin testing:

1. **Choose a demo property** from the list in [Demo environments](/connector-api/guidelines/environments.md#demo-environments).
   * Use either the Net pricing or Gross pricing variant depending on your target markets.
2. **Note the tokens** for that property:
   * `ClientToken`
   * `AccessToken`
3. **(Optional)** [Request a dedicated Demo Property](/connector-api/guidelines/environments.md#mews-operations-credentials) in **Mews Operations** to explore the UI and sample data.

You’ll use these credentials to make authenticated API requests.
{% endstep %}

{% step %}

### Make your first API call

Let’s start by calling [Get configuration](/connector-api/operations/configuration.md#get-configuration), which returns details about the test property — a useful check that your setup is working.

* **Endpoint URL**

```
https://api.mews-demo.com/api/connector/v1/configuration/get
```

* **Request body**

```json
{
  "ClientToken": "E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D",
  "AccessToken": "7059D2C25BF64EA681ACAB3A00B859CC-D91BFF2B1E3047A3E0DEC1D57BE1382",
  "Client": "NameOfYourCompanyOrApplication"
}
```

* **Expected response** If successful, the API will return HTTP status code `200 - OK` along with property details in the message body:

```json
{
  "NowUtc": "2021-05-05T11:39:29Z",
  "Enterprise": {
    "Id": "c65ea6e9-2340-42f4-9136-ab3a00b6da22",
    "Name": "Connector API Hotel (Net Pricing) TEST",
    "TimeZoneIdentifier": "America/New_York",
    "LegalEnvironmentCode": "US-DC",
    "AccommodationEnvironmentCode": "US",
    ...
  },
  "PaymentCardStorage": {
    "PublicKey": "1100016827"
  }
}
```

{% hint style="info" %}

#### Requests and responses

For more on request formatting and response codes, see [Requests](/connector-api/guidelines/requests.md) and [Responses](/connector-api/guidelines/responses.md) respectively.
{% endhint %}
{% endstep %}

{% step %}

### Learn the API essentials

#### Time and data serialization

* All dates and times are in UTC.
* Dates, durations and other data types follow specific [serialization rules](/connector-api/guidelines/serialization.md).

#### Pagination

* Some operations (like [Get all reservations](/connector-api/operations/reservations.md#get-all-reservations-2023-06-06)) use [pagination](/connector-api/guidelines/pagination.md) to handle large result sets.

#### Rate limits

* Shared demo credentials may return `429 Too many requests` response code if multiple developers are testing the same property.
* Use a different demo property if limits are reached.

#### Error handling

* Check the [response code](/connector-api/guidelines/responses.md#response-codes) and [details](/connector-api/guidelines/responses.md#error-response-details) to diagnose issues.
* Always validate required fields and timezones in your request payloads.

{% hint style="info" %}

#### Best practices

For additional tips on how to get the most out of your integration, see our best practices.
{% endhint %}
{% endstep %}
{% endstepper %}

## Next steps

Now that you've made a successful call, here’s where to go next:

* [Usage guidelines](/connector-api/guidelines.md) – How to structure requests, handle authentication, best practices, and more.
* [API Operations](/connector-api/operations.md) – Full list of API Operations.
* [API Events](/connector-api/events.md) – How to receive near-real-time event notifications.
* [Concepts](/connector-api/concepts.md) – Deeper insights into selected Mews concepts.
* [Use cases](/connector-api/use-cases.md) – Guidance on using the API for common scenarios.
* [Certification](/connector-api/your-journey/certification.md) – What’s required before going live.
* [Mews Glossary for Open API users](/getting-started/glossary.md) – Terminology for terms like *enterprise*, *customer*, and *resource*.


---

# Agent Instructions: 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:

```
GET https://docs.mews.com/connector-api/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.