Skip to content

[ING-30] feat: Document currency filter on list endpoints#534

Open
aquinofb wants to merge 1 commit into
mainfrom
feat/ing-30-currency-filter
Open

[ING-30] feat: Document currency filter on list endpoints#534
aquinofb wants to merge 1 commit into
mainfrom
feat/ing-30-currency-filter

Conversation

@aquinofb

Copy link
Copy Markdown
Contributor

Context

The lago-api backend exposes an optional currency query parameter on the subscriptions, wallets, and payment_requests list endpoints (getlago/lago-api#5249), filtering respectively by plan amount currency, wallet balance currency, and payment request amount currency. The OpenAPI spec did not document it, so the published reference and downstream SDKs had no knowledge of the filter.

Description

Adds a shared currency query parameter and references it from the GET parameters of the three list endpoints. It follows the existing filter-param convention (a file under src/parameters/ referenced by path and hoisted into components.parameters at bundle time, like payment_status and subscription_status), and sets explode: true to match sibling query params. The bundled openapi.yaml is regenerated so the published spec stays in sync with the source.

How to try locally

npm install
npm run test   # bundles src, then runs redocly + spectral lint

GET /subscriptions, GET /wallets, and GET /payment_requests now expose an optional currency query parameter.

## Context

The lago-api backend exposes an optional `currency` query parameter on
the subscriptions, wallets, and payment_requests list endpoints
(PR #5249), but the OpenAPI spec did not document it.

## Description

Add a shared `currency` query parameter (with `explode: true`, matching
sibling query params such as payment_status) and reference it from the
GET parameters of the three list endpoints. Regenerate the bundled
openapi.yaml so the published spec stays in sync with the source.
@aquinofb aquinofb self-assigned this Jun 3, 2026
@aquinofb aquinofb marked this pull request as ready for review June 8, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants