# Get started

## 1. Request API Key for test env

To start using MMS API v2 you need to become a partner first. Please get in touch with us at integrations@egym.com and we will advise you for an integration project on the proper integration path as well as the necessary keys for the APIs. If you're already a partner and have an API key then see how to [authenticate.](/mms-api-v2/authentication)

## 2. Send your members data

First, you need to push us your member data and store `accountId` from the response. `accountId` is our member identifier
which is required for ALL operations. [There](/mms-api-v2/tutorials/member-account-example) you can find examples of how to create members using
MMS API v2. Before starting implementation please ensure you read and understand [EGYM Member Account Concept](/mms-api-v2/member-account-concept).

Migration from v1 to v2 API
If you are already with EGYM and use MMS API v1 we have [migration endpoint](/mms-api-v2/apis/mms-v2/migrating-members/migrate) to migrate member by legacy user id, which will return migrated member account with accountId.

## 3. Pass acceptance tests

Request our [team](mailto:connect@egym.com) to verify published members' data in test env. If everything is working fine, we
can proceed next.

## 4. Request API Key for the pre-launch location

Next, we will provide you with the API Key for the production server, but for the pre-configured test location. Then we will
repeat steps 2 and 3.

## 5. Request API Key for the live location

Now we are ready to configure the real location. Usually, we proceed by one location at a time (Canary releases).