> 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/changelog/march-2025/march-20.md).

# March 20

### Changes

Check out the list of security changes released for Ecwid API in the last 6 months.&#x20;

These changes could break some apps, so we recommend going through the links below to ensure your application is updated or was not affected by the changes.

{% hint style="danger" %}
**Breaking changes!**\
Сhanges listed below may break some apps' logic.
{% endhint %}

<table data-header-hidden><thead><tr><th width="531.203125"></th><th></th></tr></thead><tbody><tr><td><a data-mention href="https://docs.ecwid.com/changelog/march-2025/march-20/sha1-replaced-with-sha256-for-the-storefront-sso-feature.md">SHA1 replaced with SHA256 for the Storefront SSO feature</a></td><td><a href="https://docs.ecwid.com/api-reference/">API Reference</a></td></tr><tr><td><a href="https://docs.ecwid.com/changelog/march-2025/march-20/discontinued-tokens-passing-in-query-params-of-api-calls.md">Discontinued tokens passing in query params of API calls</a></td><td><a href="https://docs.ecwid.com/api-reference/">API Reference</a></td></tr><tr><td><a href="https://docs.ecwid.com/changelog/march-2025/march-20/new-returnurl-format-in-payment-api-with-enhanced-security.md">New returnUrl format in payment API with enhanced security</a></td><td><a href="broken://spaces/bMnrDOrph8biE23TpY18">Payment methods</a></td></tr><tr><td><a href="https://docs.ecwid.com/changelog/march-2025/march-20/oauth-for-public-apps-get-request-type-changed-to-post.md">OAuth for public apps: GET request type changed to POST</a></td><td><a href="https://docs.ecwid.com/launch-apps/public-apps-overview.md">Launch apps</a></td></tr></tbody></table>


---

# 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/changelog/march-2025/march-20.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.
