Change buyer data

PATCH

/api/v2/buyers/{buyer_id}

lts

The endpoint changes the buyer data if necessary. Currently, the endpoint is used only to change the email.

Header parameters

Attribute

Requirement

Description

x-public-key

mandatory

a public key that identifies the merchant account (there can be several for one merchant)

x-buyer-ip

mandatory

is responsible for information about the buyer's IP address

x-date

mandatory

is responsible for the date and time of sending the request

x-token

mandatory

generated on the merchant side

x-source

mandatory

identifier of the type of service that is the initiator of the request

x-id

mandatory

service identifier from which the current request is made

Request parameters

Attribute

Type

Requirement

Description

Standard

buyerId

string

mandatory

Unique identifier of buyer in the system

uuid

string

mandatory

Buyer's new email

Response parameters

Depending on the success of the request, the following answers may be received:

if HTTP: 204(No content) is returned - the email has been successfully changed.
if HTTP returns: 404(Not Found) is returned - the buyer not found in the Billing database.
if HTTP: 409(Conflict) is returned - this email is ALREADY busy.
if HTTP: 422(Unprocessable Content) is returned - the email has been .