SIM Swap
Check whether the SIM card associated with a mobile number has changed within a specified time window. The result is a signal from the mobile network that your service can consider before sensitive account or payment actions.
What is SIM Swap?
A mobile number can be used to receive one-time passwords and recover access to online accounts. If that number is transferred to a different SIM or eSIM profile, someone else may be able to receive calls or messages intended for the customer.
The SIM Swap API lets your application check whether a SIM profile associated with a mobile number has changed recently. It offers two ways to do this: check whether a change happened within a chosen time window, or retrieve the date of the latest recorded change. The result gives your business an additional signal for assessing risk during sensitive customer journeys.
The API is form-factor agnostic: it covers operator-recorded changes to a subscription profile associated with a number, including physical SIMs and eSIMs. What an operator records as a change may vary by market and operator.
How it works
Your application submits a mobile number and either a look-back period or a request for the latest change date; the API returns the matching SIM-change information available for that line. Your backend calls one of the SIM Swap API operations when a customer attempts a sensitive action. You can check whether a SIM change occurred within a defined number of hours, or request the latest change date. Your application then uses the response in its own risk assessment—for example, to continue the journey, request additional verification or pause the action. The API provides information to support your decision. It does not determine whether a transaction is fraudulent or take action on an account by itself.
Why use SIM Swap
Identify a potential risk before it reaches the customer account. Check whether the SIM profile linked to a mobile number has changed recently, then use that operator signal to decide whether a sensitive action needs an additional security check.
Example Use Cases
SIM Swap fits processes that rely on a mobile number.
Deep Technical Capabilities
The CAMARA SIM Swap API provides two operations: check and retrieve-date. Both query SIM-change information for a mobile line, but return different results. CAMARA defines the API as a real-time check of the latest SIM Swap event.
Check for a SIM change within a time window
Use POST /check to ask whether a SIM change was recorded during a specified look-back period. The request can include the mobile number in E.164 format and maxAge, expressed in hours. The API returns a Boolean field:
In the CAMARA 2.1.0 specification, maxAge ranges from 1 to 2,400 hours and defaults to 240 hours if omitted. Operator privacy policies or local rules may restrict the period that can be checked; an unsupported value can result in an OUT_OF_RANGE error.
Retrieve the latest recorded change
Use POST /retrieve-date to request the timestamp of the latest recorded SIM change. The response contains latestSimChange in date-time format. If the date cannot be provided—for example, because of a market-specific retention limit—the response may contain null and a monitoredPeriod indicating the period covered by the operator’s available data.
Depending on the operator’s implementation and available history, the response may provide the SIM activation date when no later change is recorded. Do not interpret null on its own as confirmation that no SIM change ever occurred.
Interpret the result as a risk signal
A true result from check means that a change was recorded within the requested window. It does not establish that fraud has occurred. A false result means no change was reported within that check window; it does not guarantee that the account or transaction is safe.
The API reports operator-recorded SIM or eSIM subscription-profile changes. Administrative reprovisioning and other lifecycle events may be treated differently by each operator. SIM Swap does not report whether the device itself changed.
CAMARA standard, scopes and authorization
The API exposes the CAMARA check and retrieve-date operations as REST endpoints. The CAMARA 2.1.0 specification defines the scopes sim-swap:check and sim-swap:retrieve-date. Deutsche Telekom’s documentation identifies the purpose dpv:FraudPreventionAndDetection and the JWT-Bearer-tel authorization flow for its documented implementation. The applicable token flow, identifier handling and scope depend on the product setup and target market.

Simple, RESTful and built on the CAMARA standard
SIM Swap is a backend API that can be called at relevant points in an authentication, account-recovery or transaction journey. It does not send an SMS code as part of the SIM-change check. The response is an input to your application’s risk controls; the API does not block a transaction or select a step-up method for you. The required authorization flow and permitted use must be confirmed for the target market.
Before you integrate
- Confirm SIM Swap availability and supported operations in the target market.
- Decide whether your use case needs a Boolean check, the latest change date or both.
- Choose an appropriate look-back period for the
checkoperation. - Confirm market-specific data-retention limits and how the operator treats SIM-profile changes.
- Define how your application will handle a recent change, an unavailable date or an API error.
Integration steps
- Subscribe to SIM Swap for the relevant market and environment.
- Configure the required authorization flow and API scopes.
- Send the mobile number and, for
check, themaxAgevalue where applicable. - Handle the response and applicable errors, including
OUT_OF_RANGE,PERMISSION_DENIEDandTOO_MANY_REQUESTS. - Connect the result to your application’s risk rules and test with the intended customer journey.
Access requirements
- A mobile number in E.164 format when the configured authorization flow requires it.
- An active API subscription and operator support for the target market.
- An access token with the required SIM Swap scope.
- A configured authorization flow and declared purpose accepted for the product setup.
- Application logic to interpret the response and decide whether to continue, step up or review the customer action.
Application Approval Process
Each CSP must assess and approve an application’s intended use of its network APIs before granting access; TMF931 provides the standard way to submit the application and record each CSP’s decision.

Learn more about our SIM Swap API
Interested in how our SIM Swap API can help your business? Connect with a Deutsche Telekom API expert: fill out the form and we'll get back to you shortly..