Delete a customer

API at a glance

Description:
This API deletes a customer profile from Blueshift. Depending on the request, it can delete a single matching profile or multiple matching profiles.

Authentication & testing

Testing the API on this page

How to try it here

  • Use your User API Key as the Username (leave Password blank).
  • Select the appropriate API endpoint based on your Blueshift region.
  • API - Select Region
  • Enter the necessary parameters and click Try It to run the request.
Authentication using Base64 encoding

Note for developers

API requests require authentication using HTTP Basic Authentication with an API key. The API key serves as the username, while the password field should be left empty. The format to encode is: your_api_key: (note the trailing colon).

This string must be Base64-encoded and included in the request's Authorization header as follows:

Authorization: Basic encoded_value

You can generate the encoded value using a trusted Base64 encoder.


Postman collection

Try it with Postman: Explore the API using Blueshift's Postman collection.


🚧

Caution

This action is irreversible. All customer data for the specified customer will be permanently deleted.

Things to know before you start

  • Multiple profile matches:
    If multiple customer profiles match the identifier, this endpoint deletes only the first matching customer by default.

  • Delete all matching profiles:
    To delete all matching profiles, set delete_all_matching_customers=true in the API call.
    A single request can delete up to 50 profiles.

  • Deletion limit example:
    If there are 100 profiles with the same email address, one API request deletes only 50 profiles.
    Additional requests are required to delete the remaining profiles.

  • Asynchronous deletion:
    Customer data deletion is not immediate. It can take a couple of hours to complete fully across systems.

  • Use case:
    Best for permanently removing duplicate or unwanted customer profiles and fulfilling privacy or data cleanup requirements.

Request parameters

Check out the request parameters

Body parameters

Note: At least one identifier is required.

ParameterTypeRequiredDescription
emailstring❌ NoEmail address of the customer to delete.
customer_idstring❌ NoExternal customer ID of the customer.
cookiestring❌ NoCookie ID assigned to the customer by your website.
device_idstring❌ NoDevice ID linked to the customer’s mobile or web device.
delete_all_matching_customersboolean❌ NoSet to true to delete all matching customer profiles (up to 50 per request).

Example requests & responses

Delete a single matching customer
{
  "email": "[email protected]"
}
{
  "status": "ok"
}
Delete all matching customer profiles
{
  "email": "[email protected]",
  "delete_all_matching_customers": true
}
{
  "status": "ok"
}
Query Params
boolean
Body Params
string
string
Responses
200

OK

400

The request was invalid or cannot be otherwise served. An accompanying error message will explain further.

404

Resource not found. This can happen due to resource conflicts. Retry with exponential backoff. If the issue persists, contact Blueshift.

409

Conflict error, please retry. The request could not be completed due to a conflict with the current state of the target resource. Re-try with exponential backoff.

413

You can upload up to 50 users in an API call.

429

Rate limit exceeded. Too many requests. Contact us on [email protected] for recommended throughput.

500

Internal server error. Contact Blueshift for more information.

502

Service unavailable, please retry. Bad gateway. Retry with exponential backoff.

503

Service unavailable, please retry. Service unavailable. Retry with exponential backoff.

504

Service unavailable, please retry. Gateway timeout. Retry with exponential backoff.

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json