> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/contact-ecwid-api-support-team.md).

# Contact Ecwid API support team

Whether you’re developing an app for your store or Ecwid App Market, you can always count on our API Support team.&#x20;

### Get assistance with your app

If you need to update restricted app settings or have a question about your app or our API, contact API Support team directly from the app page in Ecwid admin:

1. Go to **Apps** > **Custom Apps**
2. Open the app you need help with.
3. Scroll down > **Contact Support**:<br>

   <figure><img src="https://3394277859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuOzT5egoVTAjMJwRuMQT%2Fuploads%2Fgj8HUVI0ZaCykqwBAYJU%2Fcontact_support_update_app.png?alt=media&amp;token=55494a80-aaa1-44af-b68e-49362d68d973" alt=""><figcaption></figcaption></figure>
4. Fill in the form > **Submit** button.

That’s it!

API support team will review and respond **within 24 hours** on business days. The request will automatically include your store and application IDs, enabling us to locate your app and verify its current settings. You’ll receive our response via email at the address associated with your store registration.

{% hint style="warning" %}
**Changes to access scopes do not affect existing tokens for apps already installed in a store.**\
\
Reinstall the app after any updates to application access scopes.&#x20;

To do so:

1. **Uninstall the app** from the [Ecwid admin > My apps](https://my.ecwid.com/#my_apps) page to revoke old tokens.
2. **Install the app back** from the [Ecwid admin > Custom Apps > app details](https://my.ecwid.com/#develop-apps) page to get new tokens with updated permissions.
   {% endhint %}

### Email support

Want to onboard and set up a dev environment with Ecwid? Have a question about the API documentation? Reach out to our API Support team anytime. You’ll receive a response within 1–2 business days.

Already have an Ecwid store and an app? Send us your store and application IDs to get a faster response.

[**Email us**](mailto:ec.apps@lightspeedhq.com)

### Community discussions

Chat with other developers and our API Support team on the official Ecwid Slack Community.

[**Join Ecwid Slack**](https://join.slack.com/t/lightspeed-ecom-comm/shared_invite/zt-1fsgzxsqv-1vmzH0Vb5c1cOG9rIisq4w)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecwid.com/contact-ecwid-api-support-team.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
