> 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/discontinued-tokens-passing-in-query-params-of-api-calls.md).

# Discontinued tokens passing in query params of API calls

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

#### What's new

The old way of passing access tokens in API calls is now completely disabled for all applications.

{% content-ref url="/spaces/uOzT5egoVTAjMJwRuMQT/pages/kY896vqtdWa0tqxEyfKR" %}
[Make your first API request](/get-started/make-your-first-api-request.md)
{% endcontent-ref %}

#### Changes in API

From now on, access tokens for API calls work only if passed as a Bearer token through the Authorization header.

{% tabs %}
{% tab title="API call works" %}

```http
GET /api/v3/1003/profile HTTP/1.1
Host: app.ecwid.com
Authorization: Bearer secret_token
```

where:

* `1003` - Ecwid store ID
* `secret_token` - access token of the app
  {% endtab %}

{% tab title="API call doesn't work" %}

```http
GET /api/v3/1003/profile?token=secret_token HTTP/1.1
Host: app.ecwid.com
```

where:

* `1003` - Ecwid store ID
* `secret_token` - access token of the app
  {% endtab %}
  {% endtabs %}

#### Why the changes are breaking

Making successful API calls with a token passed as a query param is now impossible. If an app still uses this approach, it can't use REST API.

#### How to update the app

1. Check if your app makes API calls.
2. If calls add an access token to the URL, remove the token from URL and add it as a `Bearer token` in the `Authorization` header instead.


---

# 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://docs.ecwid.com/changelog/march-2025/march-20/discontinued-tokens-passing-in-query-params-of-api-calls.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.