LogoLogo
  • KPN Things Portal
  • GETTING STARTED
    • About Remote SIM Provisioning
    • Concepts of RSP
    • KPN RSP Gateway APIs
  • Transparent API
    • Introduction to Transparent API
    • Connecting to Transparent APIs
    • mTLS
    • Using profiles from other vendors
    • ES2 interface description
    • ES4 interface description
  • Extended API
    • Introduction to Extended API
  • Help
    • Support
    • Release notes
Powered by GitBook

© 2025 KPN - All rights reserved.

On this page
  • General
  • ES2 - communication with SM-DP
  • Attributes
  • The interfaces
  • Getting eUICC Information 💠
  • Download a Profile 💠
  • Profile Enabling 💠
  • Profile Disabling 💠
  • Delete a Profile 💠
  • Set Fall-Back Attribute 💠

Was this helpful?

Export as PDF
  1. Transparent API

ES2 interface description

PreviousUsing profiles from other vendorsNextES4 interface description

Last updated 12 months ago

Was this helpful?

The KPN RSP Gateway has not implemented every interface of the GSMA SGP.02 v3.2 / v4.0 specification. Upon request more interfaces can be implemented. Please contact for more information.

Legend

Icon

Interface type

Source

Target

💠

Function call

Customer

KPN

🔔

Notification

KPN

Customer

General

ES2 - communication with SM-DP

Your SM-SR should be connected to our SM-DP in order to use the ES2 interface.

https://rsp.kpnthings.com/esim-messaging/3/ES2/ES2SmDpService

Attributes

  • replyTo - is considered required. Without replyTo attribute, no callback will be performed for the function call.

The interfaces

Getting eUICC Information 💠

Section 5.3.1 of the .

Allows you to retrieve up to date information of you RSP SIM card.

We check if you may access the SM-SR using the provided SM-SR ID.

Download a Profile 💠

Allows you to download a KPN profile (identifiable by ICCID or Profile type) to one of your SIM cards (identifiable by EID). You should provide the ID of the SM-SR that manages the provided SIM card.

Optionally enable the profile upon downloading the virtual profile to the SIM card.

We check if you may access the SM-SR using the provided SM-SR ID. If you download a profile using Profile type, we check whether you have access to the provided Profile type. If you download a profile using ICCID, we verify your ownership of the ICCID.

Profile Enabling 💠

Allows you to enable a profile (identifiable by ICCID) that is already downloaded to a SIM card (identifiable by EID). You should provide the ID of the SM-SR that manages the provided SIM card.

You can enable the bootstrap profile as well as the virtual profiles on the SIM card.

You will not receive a Profile Enabled notification for the profile you enable through this API call.

If you try to manage a KPN RSP SIM card, we verify your ownership of the EID. If you try to manage a non-KPN RSP SIM card, we check if you may access the SM-SR using the provided SM-SR ID.

Profile Disabling 💠

Allows you to disable a profile on a specific RSP SIM card.

If you try to control a KPN RSP SIM card, we verify your ownership of the EID. If you try to manage a non-KPN RSP SIM card, we check if you may access the SM-SR using the provided SM-SR ID.

Delete a Profile 💠

Allows you to request deletion of a profile on a specific RSP SIM card.

If you try to control a KPN RSP SIM card, we verify your ownership of the EID. If you try to manage a non-KPN RSP SIM card, we check if you may access the SM-SR using the provided SM-SR ID.

Set Fall-Back Attribute 💠

Allows you to set a profile as fallback for a specific RSP SIM card.

If you try to control a KPN RSP SIM card, we verify your ownership of the EID. If you try to manage a non-KPN RSP SIM card, we check if you may access the SM-SR using the provided SM-SR ID.

It is not possible to specify a Validity Period per request. Currently set to a fixed period of 720 seconds.

Section 5.3.2 of the .

Section 5.3.5 of the .

Section 5.3.6 of the .

Section 5.3.7 of the .

Section 5.3.23 of the .

support
SGP.02 v3.2 specification
SGP.02 v3.2 specification
SGP.02 v3.2 specification
SGP.02 v3.2 specification
SGP.02 v3.2 specification
SGP.02 v4.0 specification