Skip to content
← Back to activity

Immutable solution version

Balance transactions params fail with UnprocessableEntityError: fixed in 3.6.1

Version 2Sign in to save

Complete solution

Shows how to fix balance transactions params fail with UnprocessableEntityError: fixed in 3.6.1. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrade mollie-api-python to 3.6.1 or later; the maintainer shipped the fix there and the reporter verified the upgrade resolves it. A maintainer acknowledged it as a bug and released version 3.6.1 with the fix, and the reporter updated the package and confirmed it works.

Steps

  1. If balance.gettransactions(**params) raises UnprocessableEntityError complaining about a non-existent query parameter like params.from, while the same call works with no params, this is a client bug that mangled parameter names, not your code. Upgrade mollie-api-python to 3.6.1 or later; the maintainer shipped the fix there and the reporter verified the upgrade resolves it. If you cannot upgrade immediately, calling gettransactions() with no params works as a stopgap, since the bug only triggered when parameters were passed.

When to use

You are seeing this: Issue mollie/mollie-api-python#349 (closed, 6 comments): Passing params like from, sort, or limit to balance.get_transactions() raised UnprocessableEntityError: Non-existent query parameter "params.from" for this API call. Use this skill when you run into "Balance transactions params fail with UnprocessableEntityError: fixed in 3.6.1".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 3.6.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/mollie/mollie-api-python/issues/349

Evidence

In https://github.com/mollie/mollie-api-python/issues/349, the reporter asked: Issue mollie/mollie-api-python#349 (closed, 6 comments): Passing params like from, sort, or limit to balance.gettransactions() raised UnprocessableEntityError: Non-existent query parameter "params.from" for this API call. The client was mangling the parameter names before sending them. A maintainer acknowledged it as a bug and released version 3.6.1 with the fix, and the reporter updated the package and confirmed it works. The verified answer: If balance.gettransactions(**params) raises UnprocessableEntityError complaining about a non-existent query parameter like params.from, while the same call works with no params, this is a client bug that mangled parameter names, not your code. Upgrade mollie-api-python to 3.6.1 or later; the maintainer shipped the fix there and the reporter verified the upgrade resolves it. If you cannot upgrade immediately, calling get_transactions() with no params works as a stopgap, since the bug only triggered when parameters were passed. Source thread: https://github.com/mollie/mollie-api-python/issues/349

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_UF-UgEWBXpCt08Xgv1xZAA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Balance transactions params fail with UnprocessableEntityError: fixed in 3.6.1 <span>— Vectle</span></a>