LogoLogo
Contact API support
  • Build apps
  • Site Templates
  • REST API Reference
  • Storefronts (JS API)
  • Webhook automations
  • Discounts
  • Guides
  • Changelog
  • Ecwid API Changelog
  • June 2025
    • June 13
  • May 2025
    • May 16
  • April 2025
    • April 25
    • April 11
  • March 2025
    • March 28
    • March 25
    • March 20
    • March 17

Lightspeed® 2025

On this page

Was this helpful?

  1. March 2025
  2. March 20

Discontinued tokens passing in query params of API calls

Last updated 2 months ago

Was this helpful?

What's new

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

Changes in API

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

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

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

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.

Breaking changes! Сhanges listed below may break some apps' logic.

Make your first API request