Generate a consumer token in Klarna Payments

What this operation does

Generate a consumer token

• POSTChanges data · ordersapi.klarna.com/payments/v1/authorizations/{authorizationToken}/customer-token

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 Klarna Payments 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 Klarna Payments operations

• Create a new payment sessionPOST · changes data
• Create a new orderPOST · changes data
• Update an existing payment sessionPOST · changes data
• Cancel an existing authorizationDELETE · changes data
• Read an existing payment sessionGET · reads data

All 6 Klarna Payments operations

Questions

Can HumDay generate a consumer token in Klarna Payments?

Yes. This operation is published in Klarna Payments'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 Klarna Payments data?

Yes — this is a POST operation, so it changes something in Klarna Payments. 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 Klarna Payments account.

Where this came from

Read from a published API description for Klarna Payments at api.apis.guru/v2/specs/klarna.com/payments/1.0.0/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-25.