Delete User by External ID

curl -X DELETE \
-H "QB-Token: b284ddf44f5369611fe14e0e588f1cfa855116c8" \
https://api.quickblox.com/users/external/697.json

Empty body

{
  "errors": {
    "base": [
      "You are not allowed to modify this user"
    ]
  }
}

null

{
  "errors": {
    "id": [
      "should be a positive integer"
    ]
  }
}

DELETE

users

external

{external_user_id}

.json

curl -X DELETE \
-H "QB-Token: b284ddf44f5369611fe14e0e588f1cfa855116c8" \
https://api.quickblox.com/users/external/697.json

Empty body

{
  "errors": {
    "base": [
      "You are not allowed to modify this user"
    ]
  }
}

null

{
  "errors": {
    "id": [
      "should be a positive integer"
    ]
  }
}

Delete user by external id with API key

1. Use 'Authorization' header to pass API key

curl -X DELETE \
-H 'Authorization: ApiKey 28irlNAGasWDSupO9Vw0BBMZfuHrAUYKpmroS9yBORI' \
https://api.quickblox.com/users/external/697.json

2. As a result, the API remove a user

curl -X DELETE \
-H 'Authorization: ApiKey 28irlNAGasWDSupO9Vw0BBMZfuHrAUYKpmroS9yBORI' \
https://api.quickblox.com/users/external/697.json

integer

ID of the user in the external system ().

string

required

A user session token. See Authentication page to learn more about the session token.

string

default:"ApiKey {your_api_key}"

required

API key from Dashboard. Expected format: ApiKey {your_api_key}. Must be used either QB-Token or Authorization.

200

A successful response

401

An error response

object

Show properties

array of strings

404

An error response

422

An error response

object

Show properties

array of strings

curl -X DELETE \
-H "QB-Token: b284ddf44f5369611fe14e0e588f1cfa855116c8" \
https://api.quickblox.com/users/external/697.json

Empty body

{
  "errors": {
    "base": [
      "You are not allowed to modify this user"
    ]
  }
}

null

{
  "errors": {
    "id": [
      "should be a positive integer"
    ]
  }
}