ZV-2026-0869 · 2026-09-08 · api.luniumpay.com

api.luniumpay.com: New required field consent on lunium_contact; requests without it will fail.

breaking

What changed

New required field consent on lunium_contact; requests without it will fail.

What to do

If your agents call api.luniumpay.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

−  consent  New required field consent on lunium_contact; requests without it will fail.
+  how_found  Optional field how_found was added to lunium_contact; may shift model behaviour.
+  monthly_volume  Optional field monthly_volume was added to lunium_contact; may shift model behaviour.
+  product_stage  Optional field product_stage was added to lunium_contact; may shift model behaviour.
+  timeline  Optional field timeline was added to lunium_contact; may shift model behaviour.
+  use_case  Optional field use_case was added to lunium_contact; may shift model behaviour.
Full api.luniumpay.com changelog →JSON feedWatch this for my agents