ZV-2026-0627 · 2026-09-02 · api.ibanforge.com

api.ibanforge.com: Type of lei on lookup_bic changed unset → string|null.

breaking

What changed

Type of lei on lookup_bic changed unset → string|null. Type of city on lookup_bic changed unset → string|null. Type of lei_status on lookup_bic changed unset → string|null. Type of branch_info on lookup_bic changed unset → string|null. Type of institution on lookup_bic changed unset → string|null. Type of country_name on lookup_bic changed unset → string|null. Type of bic on lookup_ch_clearing changed unset → string|null. Type of qr_iid on lookup_ch_clearing changed unset → string|null. Type of sic_iid on lookup_ch_clearing changed unset → string|null. Type of valid on validate_payment_reference changed unset → boolean|null. Type of scheme on validate_payment_reference changed unset → string|null. Type of source on validate_payment_reference changed unset → string|null.

What to do

If your agents call api.ibanforge.com, pin the new snapshot, patch the affected call sites, and let a green contract check confirm the fix. If you don't use the changed tools, nothing is required, but the rest of the ecosystem just learned about it at the same moment you did.

The redline

−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_bic
−  unset
+  string|null   lookup_ch_clearing
−  unset
+  string|null   lookup_ch_clearing
−  unset
+  string|null   lookup_ch_clearing
−  unset
+  boolean|null   validate_payment_reference
−  unset
+  string|null   validate_payment_reference
−  unset
+  string|null   validate_payment_reference
Full api.ibanforge.com changelog →JSON feedWatch this for my agents