Remove the current tier from a customer

{ "ErrorMessage": "<string>", "ErrorCode": 123, "Result": { "MessageResult": "<string>", "OldTierName": "<string>" }, "Code": "<string>", "CodeName": "<string>", "HasWarning": true, "HasError": true }

Some important remarks

If the customer does not exist, the API returns an error with the Customer_NotFound error code.

If the customer does not have any tier assigned, the response MessageResult will be "The consumer does not have a tier to remove.".

If the customer is already on the base tier, the tier cannot be removed. The response MessageResult will be "The consumer is on the base tier and does not have a tier to remove".

On success, the customer is automatically assigned to the base tier and the response MessageResult will be "Tier removed successfully.".

Authorizations

Authorization

string

header

required

Use API Basic Auth Keys

Path Parameters

originalId

string

required

Id from the client's store, usually email address or document

Response

200 - application/json

The result of the removal including MessageResult and OldTierName, or an error response

Standard response envelope used by the External API.

ErrorMessage

string | null

Error message returned when the request fails validation or processing. For warnings and successful responses, consumers should usually inspect Result, Code and Severity first.

ErrorCode

integer<int32> | null

Legacy numeric error code derived from internal API errors when available. This field is relevant only for error flows that use ApiResponseErrorDescription.

Result

object

Business payload returned by the endpoint.

Show child attributes

Code

string | null

Endpoint-specific business code formatted as a two-digit string, such as 03 or 07. This field is available for success, warning and error outcomes.

CodeName

string | null

Symbolic enum name associated with Code, such as CheckoutNotFound.

Severity

enum<integer>

Final severity of the response. Success means the action completed as expected, Warning means the request was valid but the business outcome is informational or non-ideal, and Error means the request should be treated as a failure.

Available options:

0,

1,

2

HasWarning

boolean

Convenience flag that is true when Severity is Warning. Warnings are valid 200 OK business outcomes and should not be handled as transport or validation errors.

HasError

boolean

Indicates whether the request failed and should be handled as an error response. This flag is reserved for real API errors; warnings must keep this property as false.