Skip to main content
GET /v1/organizations/{slug} and GET /v2/organizations/{slug} will be sunset on September 15, 2026. Migrate to GET /v2/organization before that date.

​
What is changing

Both deprecated endpoints already emit Sunset, Deprecation, and Link response headers so well-behaved clients can detect the upcoming retirement programmatically. After September 15, 2026 both endpoints will respond with 410 Gone.

​
Who is affected

Any integration calling either of the following URLs:
  • GET /v1/organizations/{slug}
  • GET /v2/organizations/{slug}

​
Feature parity

GET /v2/organization is backed by the same handler as the deprecated routes, so it returns the same underlying data. The OAuth scope (organization.read) is unchanged. There is one interface difference: the {slug} path parameter is removed. Your OAuth token already identifies the organization, so the URL slug was effectively redundant — the gateway always resolved requests to the authenticated organization regardless of what you passed in the path.
The slug is still returned in the response body at organization.slug, so any client code that reads the slug keeps working.

​
Step-by-step migration

1

Swap the URL

Replace /v1/organizations/{slug} or /v2/organizations/{slug} with /v2/organization and drop the slug from the path. The response is resolved from the authenticated organization.
2

Keep the same OAuth scope

organization.read — unchanged.
3

Read the slug from the response if you still need it

organization.slug remains in the response body.
4

(Optional) Adopt the richer v2 response

GET /v2/organization also exposes extra fields (id, name, locale, legal_*, contract_signed_at, additional bank-account fields) and an optional include_external_accounts query parameter. None of this is required — ignore fields you don’t need.
5

Watch the deprecation signals

Until the cutover, monitor the Sunset, Deprecation, and Link response headers on the deprecated endpoints to automate migration reminders in your infrastructure.

​
Before / after

curl -H "Authorization: Bearer $TOKEN" \
  https://thirdparty.qonto.com/v1/organizations/$SLUG

# or

curl -H "Authorization: Bearer $TOKEN" \
  https://thirdparty.qonto.com/v2/organizations/$SLUG

​
Response headers on the deprecated endpoints

Until the sunset date, every response from the deprecated endpoints includes: 
Sunset: Tue, 15 Sep 2026 23:59:59 GMT
Deprecation: @1789495199
Link: <https://docs.qonto.com/api-reference/business-api/accounts-organizations/organizations/migrate-from-deprecated-organization-endpoints>; rel="deprecation",
      <https://thirdparty.qonto.com/v2/organization>; rel="successor-version"
These follow RFC 8594 (Sunset) and RFC 9745 (Deprecation).

​
Timeline

  • Today: deprecated endpoints return the new Sunset / Deprecation / Link headers and continue to serve 200 OK.
  • September 15, 2026: deprecated endpoints return 410 Gone.