Delete merchant user

Removes a merchant user from the system. Supports both soft delete (default) and hard delete options

DELETE/api/v1/{team_slug}/{app_slug}/merchant-users/{user_id}

management-api:DELETE:/api/v1/{team_slug}/{app_slug}/merchant-users/{user_id}

Removes a merchant user from the system. Supports both soft delete (default) and hard delete options

API ownership

API family: Management API
Best for: Trusted back-office workflows that create, update, organize, or delete merchant-owned data.
Do not use from: Browser-only storefront code or public clients.
Guide route: /apis/management/latest

The OpenAPI contract defines the method, path, parameters, request body, and responses for this operation.

Method: DELETE
Path: /api/v1/\{team_slug\}/\{app_slug\}/merchant-users/\{user_id\}
Summary: Delete merchant user
Description: Removes a merchant user from the system. Supports both soft delete (default) and hard delete options
OpenAPI contract: management-api
Operation ID: Not documented in the OpenAPI contract.

Operation key uses API family, method, and path because this OpenAPI contract does not publish an operation ID.

Parameters3 parameters

Name	In	Required	Type	Description
app_slug	path	Yes	string	App slug
team_slug	path	Yes	string	Team slug
user_id	path	Yes	string	Merchant user ID

Request bodyDocumented body

Property	Type	Required	Details
`hard_delete`	boolean	No	-

Generated example (synthetic):

{
  "hard_delete": false
}

Responses5 statuses

Status	Description	Content
200	User deleted successfully	application/json (object)
400	Invalid request (e.g. bad user ID format)	application/json (object)
401	Unauthorized access	application/json (object)
404	User not found	application/json (object)
500	Internal server error	application/json (object)

Property	Type	Required	Details
`data`	string	No	-
`details`	string[]	No	Additional contextual information about the response. Used to provide supplementary details beyond the main data payload, such as validation warnings or processing notes
`success`	boolean	No	-

Generated example (synthetic):

{
  "data": "string",
  "details": [
    "string"
  ],
  "success": false
}

Property	Type	Required	Details
`details`	string[]	No	-
`message`	string	No	-
`success`	boolean	No	-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

Property	Type	Required	Details
`details`	string[]	No	-
`message`	string	No	-
`success`	boolean	No	-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

Property	Type	Required	Details
`details`	string[]	No	-
`message`	string	No	-
`success`	boolean	No	-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

Property	Type	Required	Details
`details`	string[]	No	-
`message`	string	No	-
`success`	boolean	No	-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

Use these fields to confirm you are implementing the intended endpoint contract.