Internal server error on reimbursement API for some IDs

[gpr-indevelopment]

What is the problem?
I found that some document IDs trigger an internal server error (status 500) from Jarbas' reimbursement API. For example, the following request returns 500 for ID 1681601:

GET https://jarbas.serenata.ai/api/chamber_of_deputies/reimbursement/1681601/

The same happens for IDs: 1633216, 1681597, 1681598, 1681600, 1681599. These are valid document codes from the chamber of deputies database of expenses:

How can this be addressed?
It all depends on the cause of the internal server error. The exception firing the 500 status should be addressed on Jarbas' side.
I would suggest trying to reproduce the given scenario to see what is the exception thrown.

Labels
[first-timers-only] [bug]