> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stora.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a test operator

> Create an operator for development, prepare test data, and choose credentials for your integration.

Use a test operator to build and test your integration without connecting a real operator account. Test operators belong to your developer company.

## Before you start

Sign in to the [Developer Portal](https://developer.stora.co). To create an operator, you need the **Admin** role in your developer company.

The portal shows how many test operators your company has used and its current limit. If the company has reached that limit, contact Stora before creating another operator.

## Create the operator

1. Open **Test operators**.
2. Click **New operator**.
3. Select the **Country**.
4. Check the **Timezone** and **Locale** for that country. Choose values that match the behavior you need to test.
5. Click **Create operator**.

The operator appears in the list. Your company's test partner applications can use it automatically. You do not need an operator testing invitation.

## Prepare test data

1. In the operator's **Actions** menu, click **Open Backoffice**.
2. Check the sites, unit types, and units available to your test operator. Add or configure the records your integration needs in Backoffice.
3. If you test a booking journey, return to **Test operators** and click **Open Storefront** to inspect the customer-facing flow.

Keep test data separate from production data. Use fictional contact details and test credentials in your development environment.

> [!NOTE]
>
> Creating a test operator does not connect a real operator or grant access to a real operator's data. For an integration you manage on an operator's behalf, [connect an account](https://docs.stora.co/2025-09/guides/connect-account.md). For a pilot of a partner app, [invite the operator to test that app](https://docs.stora.co/2025-09/guides/partner-integrations.md#invite-a-real-operator-to-test).

## Create credentials

Choose the authentication flow that your production integration uses.

* For an Access Token or Client Credentials integration, click **Manage credentials** in the operator's **Actions** menu. Follow [API credentials](https://docs.stora.co/2025-09/guides/managed-account-authentication.md) to create credentials with the scopes you need.
* For a partner integration, create a test app under **My applications**. Use that app's credentials in the [Authorization Code flow](https://docs.stora.co/2025-09/guides/authentication.md#option-c-oauth-2-0-%E2%80%94-authorization-code), then authorise the test operator. Do not substitute an Access Token for the flow you need to test.

Store credentials on your backend, outside source control. Keep test app credentials separate from live app credentials.

## Verify access

[Make your first request](https://docs.stora.co/2025-09/guides/first-request.md) with the test operator's credentials. Confirm that the response contains the operator and records you expect before testing writes.

If your integration receives events, configure a [webhook endpoint](https://docs.stora.co/2025-09/guides/webhooks.md) for this operator. A webhook endpoint for a different operator does not cover this one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.