Klarna Partner Product API - Interoperability (v2/r6)

Download OpenAPI specification:Download

Interoperability API

Interoperability refers to the ability of Klarna's full product suite to work seamlessly across multiple integration paths.

Generate SDK token

Returns an sdk_token that can be used to initialize Web SDK or Mobile SDK in order to personalize customer experience.


SLO Category: The SLO Service Category. Operations that handle all aspects of a Payment Request, including creation, retrieval, updates, and deletion.Payment Request
SLA Service Class: The SLA Service Class this operation is classified at when evaluating SLA compliance. Operations, webhooks and other services that are outside the scope of both Transaction Critical and Transaction Non-critical OperationsAdditional Services
Lifecycle Stage: The Lifecycle Stage tag in operations and attributes defines completeness of the feature for usage Feature under development, may not be fully available and is subject to change as we continue building the service in partnership with early usersEarly Release
Availability in Test environment: Indicates if the feature is available in the Klarna Test environment Feature is not available in the Klarna Test environmentNot available
Availability in Production environment: Indicates if the feature is available in the Klarna Production environment Feature is not available in the Klarna Production environmentNot available

Securityklarna_api_key
Request
path Parameters
partner_account_id
required
string (AccountIdentifier)

The unique identifier of the account for which the action is performed.

Example: krn:partner:global:account:live:LWT2XJSE
header Parameters
Klarna-Interoperability-Token
required
string (InteroperabilityToken) <= 8192 characters

The interoperability token enables continuity of customer journey across domains and services.

Example: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzaG9wcGluZ19zZXNzaW9uX2lkIjoia3JuOnNob3BwaW5nOmV1MTpzZXNzaW9uOjBlOTIyN2MwLTBjNDAtNDdkZi04YzEwLTQwMTRmYzFiZDJiZCIsInN0YXR1cyI6IlBBWU1FTlRfUFJFUEFSRUQiLCJ2ZXJzaW9uIjoxLCJjcmVhdGVkX2F0IjoiMjAyNC0wMS0wMVQxMjowMDowMFoiLCJ1cGRhdGVkX2F0IjoiMjAyNC0wMS0wMVQxMjowMDowMFoifQ.1y87kuEKnETy_UCHbTMXx1p4mViZE816okcVmfHFZoo
object

Metadata about the integrator and originators of the request, serialized as a valid JSON, to improve troubleshooting. Read more here

Example: integration_metadata=[object Object]
Partner-Correlation-Id
string <= 255 characters ^[A-Za-z0-9]+$

An optional alpha numerical String that the partner can use to correlate. This value will be returned in the response.

Responses
200

SDK token

400

Bad Request, there was an error in the input of the request. The request can not be retried without modifications.

401

Unauthorized, the request was not authorized.

404

Not Found, the requested resource was not found.

429

Too Many Requests, the request was rate limited.

500

Internal Server Error, there was an unexpected error in the API.

503

Service Temporarily Unavailable, the system is temporarily unavailable to process the request.

post/v2/accounts/{partner_account_id}/interoperability/sdk-tokens
Request samples
Response samples
application/json
{
  • "sdk_token": "hbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9zaG9wcGluZ19zZXNzaW9uX2lkIjoia3JuOnNob3BwaW5nOmV1MTpzZ"
}