Affects
Teams integrating with the Lerian Consignado — Dataprev API, and teams operating its deployment.
What changed
Three operations are new. Record a correction to a registered contract and download the corrected resource it names — this repairs a wrong CCB or a disbursement confirmation with wrong evidence, and it crosses no government boundary. Exclude a contract from your institution because the worker ported it out, the origin-side counterpart of the portability averbação you already had. Refinancing reversal is narrower and its request body changed. The optional
dataRefinanciamento field is gone. The 7-business-day window is now judged against the gateway’s own record of when the refinancing committed, never against a date in the request. Only a refinancing this gateway registered can be reversed through it; anything else is refused with 404 before Dataprev is called.
The formalization portal is optional. A tenant with a registered worker portal base URL still gets it injected as the type 0 contact of every bid proposal. A tenant without one now bids anyway, carrying only the client’s own contacts, and the bid is refused only when there is neither a registered portal nor a single contact. A bid can also carry its own portalBaseUrl to override the tenant’s registered portal for that submission alone. Client-supplied type 0 contacts remain forbidden in every case.
Error codes now use the CLT- prefix. The numbers are unchanged: what was MYS-0006 is CLT-0006.
Corrections to the published operations guide. The gateway runs eleven scheduled loops, not eight — the three that were missing are the portability discovery poller and the two outcome-recovery loops, both disabled by default. The Lender command stream carries three keys, not two, and the keys use an underscore in the resource segment (consignado_margin.requested). All 25 business facts have a production emission site; the earlier statement that two portability outcomes were conditional on a manifest declaration was wrong. AWS_REGION has no default, deliberately, so the AWS SDK can resolve your own region.
Impact
Classification: Action required.
What you need to do
1
Remove
dataRefinanciamento from refinancing-reversal requests, and confirm every refinancing you intend to reverse was registered through this gateway.2
Update any error handling that matches on the
MYS- prefix to match CLT- instead.3
If your tenant has no registered portal base URL, make sure every bid proposal carries at least one contact of type 1 through 4.
4
Enable the averbação and rail-command recovery loops in any deployment that submits rail commands, and set
AWS_REGION explicitly for the region your data must stay in.