> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/getting-started-guide/member-registartion-configuration.md).

# Member Registration Configuration

## How this example works

OpenLoyalty supports multitenancy, allowing each tenant (store) to operate as a distinct database, complete with its own member list and campaigns. This guide outlines the initial step of the setup process: selecting the appropriate registration method for a member. A single unique identifier is required, which can be an email, phone number, or loyalty card number (that can serve as your own unique identifier).

***

## Try yourself <a href="#to-try-it-yourself" id="to-try-it-yourself"></a>

* Input the previous saved [token](/technical-guide/getting-started-guide/authentication.md) in the request header
* Retrieve a list of [tenants (stores)](/main-features/settings/tenants.md)\
  Endpoint: `GET /api/store`
* Choose the required tenant and its code
* Retrieve member registration for the specified tenant\
  Endpoint: `GET /api/{storeCode}/settings`
* Update `identificationMethod`\
  Endpoint: `PATCH /api/{storeCode}/settings`

  ```

  {
      "settings": {
          "identificationMethod": "phone" // or "loyaltyCardNumber", "email"
      }
  }

  ```

Moving forward, the chosen method will be a required field for member registration.

{% hint style="info" %}
Please ensure the proper configuration of the tenant. You can find out more [in this article](https://help.openloyalty.io/main-features/members/member-list/configuration).
{% endhint %}

***

## Endpoints used

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/store" method="get" %}
[openapi-5.61.0 (1).json](https://content.gitbook.com/content/gIv2CyIIYf7vRfuhMKQ6/blobs/2xnMWXnOETp8Vxl2YZoi/openapi-5.61.0%20\(1\).json)
{% endopenapi %}

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/{storeCode}/settings" method="get" %}
[openapi-5.61.0 (1).json](https://content.gitbook.com/content/gIv2CyIIYf7vRfuhMKQ6/blobs/2xnMWXnOETp8Vxl2YZoi/openapi-5.61.0%20\(1\).json)
{% endopenapi %}

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/{storeCode}/settings" method="patch" %}
[openapi-5.61.0 (1).json](https://content.gitbook.com/content/gIv2CyIIYf7vRfuhMKQ6/blobs/2xnMWXnOETp8Vxl2YZoi/openapi-5.61.0%20\(1\).json)
{% endopenapi %}

***

## More resources

For a detailed overview and description of the member registration configuration, please refer to these articles:

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/j48yqHrYfv39cNFAHNej" %}
[Tenants](/main-features/settings/tenants.md)
{% endcontent-ref %}

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/Zyn32QzPx6qiUOfPrYRA" %}
[Broken mention](broken://spaces/cNVX03KZzmrGwJihLiEx/pages/Zyn32QzPx6qiUOfPrYRA)
{% endcontent-ref %}

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/-MZBtB6mVs\_9AWRBvBZ-" %}
[Settings](/main-features/settings.md)
{% endcontent-ref %}


---

# 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://help.openloyalty.io/technical-guide/getting-started-guide/member-registartion-configuration.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.