---
title: "Changes to Route liquidity limit"
method: GET
path: "/liquidity"
---

# Changes to Route liquidity limit

`GET /liquidity`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 5 of 17 revisions.

- **2026-06-25** `3656a04f8c42`: 9 breaking, 2 warning, 17 info
- **2026-06-05** `36737b6b49a4`: 3 breaking
- **2026-05-28** `c11fcf5d44dc`: 2 breaking, 3 info
- **2026-05-08** `618cc05f65ca`: 9 breaking, 4 info
- **2026-04-21** `71e21fa054d5`: 1 info

## Changes

- **2026-06-25** `3656a04f8c42`: 9 breaking, 2 warning, 17 info
  - the `x-api-version` request header's property undefined was restricted to a list of enum values
  - the `header` request parameter `x-api-version` was restricted to a list of enum values
  - the `header` request parameter `x-api-version` became required
  - for the `query` request parameter `destinationToken`, the minLength was increased from `0` to `1`
  - for the `query` request parameter `destinationChainId`, the type changed from `string` to `integer`
  - for the `query` request parameter `sourceChainId`, the type changed from `string` to `integer`
  - the response's body type changed from no type to `object` for status `400`
  - the response's body type changed from no type to `object` for status `403`
  - the response's body type changed from no type to `object` for status `500`
  - for the `query` request parameter `destinationChainId`, the min was set to `1.00`
  - for the `query` request parameter `sourceChainId`, the min was set to `1.00`
  - api operation id `listLiquidity` was added
  - added the new enum value `2026-01.alps` to the `header` request parameter `x-api-version`
  - removed the pattern `^\d{4}-\d{2}\.[a-z0-9]+$` from the `header` request parameter `x-api-version`
  - removed the pattern `^eip155:\d+$` from the `query` request parameter `destinationChainId`
  - removed the pattern `^eip155:\d+$` from the `query` request parameter `sourceChainId`
  - removed response discriminator for the response status `400`
  - removed response discriminator for the response status `403`
  - removed response discriminator for the response status `500`
  - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `400`
  - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `403`
  - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `500`
  - added the required property `errors` to the response with the `400` status
  - added the required property `errors` to the response with the `403` status
  - added the required property `errors` to the response with the `500` status
  - added the required property `traceId` to the response with the `400` status
  - added the required property `traceId` to the response with the `403` status
  - added the required property `traceId` to the response with the `500` status
- **2026-06-05** `36737b6b49a4`: 3 breaking
  - added `subschema #2` to the response body `oneOf` list for the response status `400`
  - added `subschema #2` to the response body `oneOf` list for the response status `403`
  - added `subschema #2` to the response body `oneOf` list for the response status `500`
- **2026-05-28** `c11fcf5d44dc`: 2 breaking, 3 info
  - added `subschema #1, subschema #2, subschema #3, subschema #4` to the response body `oneOf` list for the response status `400`
  - added `subschema #1, subschema #2, subschema #3, subschema #4` to the response body `oneOf` list for the response status `500`
  - removed `subschema #1, subschema #2, subschema #3` from the response body `oneOf` list for the response status `400`
  - removed `subschema #1, subschema #2, subschema #3` from the response body `oneOf` list for the response status `500`
  - added the non-success response with the status `403`
- **2026-05-08** `618cc05f65ca`: 9 breaking, 4 info
  - added the pattern `^eip155:\d+$` to the `query` request parameter `destinationChainId`
  - added the pattern `^eip155:\d+$` to the `query` request parameter `sourceChainId`
  - added `subschema #1, subschema #2, subschema #3` to the response body `oneOf` list for the response status `400`
  - added `subschema #1, subschema #2, subschema #3` to the response body `oneOf` list for the response status `500`
  - the response's body type changed from `object` to no type for status `400`
  - the response's body type changed from `object` to no type for status `500`
  - removed the required property `error` from the response with the `500` status
  - removed the required property `errors` from the response with the `400` status
  - removed the required property `traceId` from the response with the `400` status
  - for the `query` request parameter `destinationChainId`, the type was generalized from `integer` to `string`
  - for the `query` request parameter `sourceChainId`, the type was generalized from `integer` to `string`
  - added response discriminator for the response status `400`
  - added response discriminator for the response status `500`
- **2026-04-21** `71e21fa054d5`: 1 info
  - endpoint added

---

[Operation](https://skmtc.dev/rhinestonewtf/apis/rhinestone-orchestrator-api/docs/liquidity/get.md) - [API](https://skmtc.dev/rhinestonewtf/apis/rhinestone-orchestrator-api.md) - [Page](https://skmtc.dev/rhinestonewtf/apis/rhinestone-orchestrator-api/changes/liquidity/get)