> For the complete documentation index, see [llms.txt](https://docs.simplestore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplestore.io/front-end-client-apis.md).

# Front End Client APIs

Client APIs support the implementation of the Simple Store API into public facing channels like a web or mobile application.

### API Key

All Front End Client APIs must include an API Key which is associated with your Simple Store (Tenant) Account.

the API key is passed onto each request using the header: x-api-key

### Token Authentication

A subset of the Client API support functionality tied to specific customers, examples include:

* Change Customer Details
* Change Password
* Get Order History

A token is issued by calling the [\[login\]](https://clients.api.simplestore.io/swagger/index.html#/Customer/Customer_Login) method on the Client API:

```bash
curl -d '{"emailAddress":"email address", "password":"password"}' \
     -H "Content-Type: application/json" \
     -H "x-api-key: [api-key]"
     -X POST https://clients.api.simplestore.io/v1/customer/login
```

### Swagger References

<https://clients.api.simplestore.io/swagger/index.html>


---

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

```
GET https://docs.simplestore.io/front-end-client-apis.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.