---
title: "Check SIM Swap"
method: POST
path: "/network/sim-swap"
tags: ["network > simSwap"]
---

# Check SIM Swap

`POST /network/sim-swap`

## Request

- Base URL: `https://api.pinnacle.sh`
- URL: `https://api.pinnacle.sh/network/sim-swap`
- Auth: API key in header `PINNACLE-API-KEY`

Check whether a phone number's SIM was changed during a recent lookback window. Use this to flag account takeover risk before sign-in, password reset, payment, or other sensitive actions.

<Note>
  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
</Note>

## Request body

- SimSwapRequest
  - `phoneNumber` string, required: Phone number in E.164 format, including country code.
  - `periodHours` integer: Lookback window, in hours, for detecting a recent SIM change. Must be from 1 to 2400. Defaults to 240.

## Response `200`

Returns SIM swap risk for the requested phone number.

- SimSwapResponse
  - `requestId` string, required: Unique Pinnacle ID for a Network API request.
  - `status` 'available' | 'unavailable' | 'unsupported' | 'failed', required: Availability of the carrier-backed insight.
  - `simSwapped` boolean, nullable, required: Whether the SIM changed during the requested window. Null means the carrier insight was unavailable, unsupported, or failed.
  - `latestSimSwapAt` string, date-time, nullable, required: Timestamp of the latest SIM change in the requested window, when the carrier provides it.

## Other responses

- `400`: The request was unacceptable, often due to providing an invalid update. <br> Errors may originate from invalid payload or from Pinnacle's additional validation checks. For example, providing an URL that cannot be accessed, updating a campaign that is currently being reviewed, updating data that you cannot access, sending a malformed message, and so on. <br> For `Pinnacle Validation Error` inspect the `error` payload to determine the source of the failure. These errors are likely due to additional validation and business logic checks.<br> For `Request Validation Error` inspect the `description` and `errors` payload to determine the source of failure. These errors are likely due to invalid payload inside the request.
- `401`: The request lacks valid authentication credentials or the provided credentials are invalid. <br> Ensure you're including a valid API key in the request headers and that your account has the necessary permissions to access this endpoint.
- `403`: Your subscription does not include access to this feature. <br> This occurs when attempting to use functionality that requires a higher subscription tier. Please upgrade your subscription to access this feature.
- `500`: An unexpected error occurred on Pinnacle's servers while processing your request. <br> If this error persists, please contact support with the request details.

---

[API](https://skmtc.dev/pinnacle/apis/pinnacle-2.md) - [All operations](https://skmtc.dev/pinnacle/apis/pinnacle-2/llms.txt) - [OpenAPI document](https://skmtc.dev/pinnacle/apis/pinnacle-2/revisions/45416dadab79?raw)