Carts/mine/payment-information in Magento B2B

What this operation does

carts/mine/payment-information

• POSTChanges data · carts/mine/payment-informationexample.com/V1/carts/mine/payment-information

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Magento B2B operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Magento B2B operations

• Orders/createPUT · changes data
• Invoices/commentsPOST · changes data
• Orders/{id}/emailsPOST · changes data
• Invoices/{id}/emailsPOST · changes data
• Orders/{id}/commentsPOST · changes data
• Order/{orderId}/invoicePOST · changes data
• Customers/{email}/activatePUT · changes data
• Customers/mePUT · changes data

All 455 Magento B2B operations

Questions

Can HumDay carts/mine/payment-information in Magento B2B?

Yes. This operation is published in Magento B2B's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Magento B2B data?

Yes — this is a POST operation, so it changes something in Magento B2B. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Magento B2B account.

Where this came from

Read from a published API description for Magento B2B at devdocs.magento.com/redoc/2.2/latest-2.2.schema.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.