---
title: "Depersonalize push instance"
method: POST
path: "/people/2/contactInformation/push/{pushRegId}/depersonalize"
tags: ["customer-engagement", "people", "contact-information:-push"]
---

# Depersonalize push instance

`POST /people/2/contactInformation/push/{pushRegId}/depersonalize`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/people/2/contactInformation/push/{pushRegId}/depersonalize`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

You can depersonalize a device to detach it from a current person profile so that the device won’t receive messages when targeted by any of the person attributes

## Path parameters

- `pushRegId` string, required

## Headers

- `AppCode` string, required

## Response `200`

OK

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)