Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LedgerAccountSettlementListParams - Provide created_at, updated_at for filtering? #421

Closed
jcarlsonautomatiq opened this issue Jun 27, 2024 · 2 comments

Comments

@jcarlsonautomatiq
Copy link

Would it be possible to get filters on creation / updates into the API for the settlement transactions? Currently we are using a settlement to rollup a week of order information but if we get a year in we are going to have a lot of settlements. Does the API already have undocumented params we can use per the guide?

Under:
https://docs.moderntreasury.com/platform/reference/list-ledger-account-settlements

/**
  • Use gt (>), gte (>=), lt (<), lte (<=), or eq (=) to filter by the
  • posted at timestamp. For example, for all times after Jan 1 2000 12:00 UTC, use
  • updated_at%5Bgt%5D=2000-01-01T12:00:00Z.
    */
    updated_at?: Record<string, string>;
    created_at?:Record<string, string>
export interface LedgerAccountSettlementListParams extends PageParams {
  /**
   * If you have specific IDs to retrieve in bulk, you can pass them as query
   * parameters delimited with `id[]=`, for example `?id[]=123&id[]=abc`.
   */
  id?: Array<string>;

  ledger_transaction_id?: string;

  /**
   * For example, if you want to query for records with metadata key `Type` and value
   * `Loan`, the query would be `metadata%5BType%5D=Loan`. This encodes the query
   * parameters.
   */
  metadata?: Record<string, string>;

  settled_ledger_account_id?: string;

  settlement_entry_direction?: string;
}
@kmurase
Copy link

kmurase commented Jun 27, 2024

Hey @jcarlsonautomatiq - I'm the PM for Ledgers. We're looking into if we can slot this change into the roadmap for you, we'll keep you posted. Git comments can sometimes slip through the cracks but for future requests if you ping [email protected] it'll get back to me!

@jcarlsonautomatiq
Copy link
Author

Thanks! I looked around for an API 'please contact us this way' and probably missed that method of communication :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants