Skip to main content
PUT
Update Customer

Authorizations

Authorization
string
header
required

All requests must include the static API Key in the Authorization header using the Bearer scheme.

Headers

Restoo-Partner-Id
string
required

Unique identifier of your Partner account (defined by Restoo).

Restoo-Account-Id
string
required

Unique identifier of the Tenant.

Path Parameters

customerUuid
string
required

The customer UUID

Example:

"50b5571be67b477baa9dead4b290c555"

Body

application/json

UpdateCustomerRequest

Request to update a customer's data.

Whether the Customer consents to their personal data being processed so the venue can manage the Booking. Not the marketing consent — that is acceptsMarketing.

false is not accepted: without consent there is no Customer, and so no Booking. Withdrawing a consent already given is not something this API exposes yet, and a Customer who has withdrawn it stops appearing in Customer search

Example:

true

acceptsMarketing
boolean
required

Indicates whether the Customer has consented to receive marketing communications

Example:

true

name
string
required

The full name of the Customer

Required string length: 3 - 255
Example:

"Steve Jobs"

email
string<email>
required

The Customer's email address

Maximum string length: 255
Example:

"steve.jobs@restoo.me"

phone
string
required

The Customer's phone number in E.164 format

Example:

"+34600111222"

birthDate
string<date> | null

Date of birth of the Customer in ISO 8601 format (YYYY-MM-DD)

Example:

"1979-03-20"

postalCode
string | null

The Customer's postal code

Maximum string length: 12
Example:

"28045"

language
enum<string>

The preferred language of the Customer, represented as an ISO 639-1 code

Available options:
es,
ca,
it,
en,
de,
fr,
pt,
eu
Example:

"en"

country
enum<string>

The country of the Customer, represented as a two-letter ISO 3166-1 alpha-2 code

Available options:
AF,
AX,
AL,
DZ,
AS,
AD,
AO,
AI,
AQ,
AG,
AR,
AM,
AW,
AU,
AT,
AZ,
BS,
BH,
BD,
BB,
BY,
BE,
BZ,
BJ,
BM,
BT,
BO,
BQ,
BA,
BW,
BV,
BR,
IO,
BN,
BG,
BF,
BI,
CV,
KH,
CM,
CA,
KY,
CF,
TD,
CL,
CN,
CX,
CC,
CO,
KM,
CG,
CD,
CK,
CR,
CI,
HR,
CU,
CW,
CY,
CZ,
DK,
DJ,
DM,
DO,
EC,
EG,
SV,
GQ,
ER,
EE,
SZ,
ET,
FK,
FO,
FJ,
FI,
FR,
GF,
PF,
TF,
GA,
GM,
GE,
DE,
GH,
GI,
GR,
GL,
GD,
GP,
GU,
GT,
GG,
GN,
GW,
GY,
HT,
HM,
VA,
HN,
HK,
HU,
IS,
IN,
ID,
IR,
IQ,
IE,
IM,
IL,
IT,
JM,
JP,
JE,
JO,
KZ,
KE,
KI,
KP,
KR,
XK,
KW,
KG,
LA,
LV,
LB,
LS,
LR,
LY,
LI,
LT,
LU,
MO,
MG,
MW,
MY,
MV,
ML,
MT,
MH,
MQ,
MR,
MU,
YT,
MX,
FM,
MD,
MC,
MN,
ME,
MS,
MA,
MZ,
MM,
NA,
NR,
NP,
NL,
NC,
NZ,
NI,
NE,
NG,
NU,
NF,
MK,
MP,
NO,
OM,
PK,
PW,
PS,
PA,
PG,
PY,
PE,
PH,
PN,
PL,
PT,
PR,
QA,
RE,
RO,
RU,
RW,
BL,
SH,
KN,
LC,
MF,
PM,
VC,
WS,
SM,
ST,
SA,
SN,
RS,
SC,
SL,
SG,
SX,
SK,
SI,
SB,
SO,
ZA,
GS,
SS,
ES,
LK,
SD,
SR,
SJ,
SE,
CH,
SY,
TW,
TJ,
TZ,
TH,
TL,
TG,
TK,
TO,
TT,
TN,
TR,
TM,
TC,
TV,
UG,
UA,
AE,
GB,
UM,
US,
UY,
UZ,
VU,
VE,
VN,
VG,
VI,
WF,
EH,
YE,
ZM,
ZW
Example:

"ES"

Response

PrivateCustomerResponse

PublicCustomerResponse

Private Customer details.

privateNotes
string | null
required

Internal notes about the customer, visible only to venue staff

Maximum string length: 2048
Example:

"Customer prefers a table near the terrace."

visitFrequency
integer | null
required

Average frequency of visits, expressed as the number of days between visits

Required range: x >= 0
Example:

30

averageOrderAmountPerPax
integer | null
required

Average order amount per guest (in cents)

Required range: x >= 0
Example:

4500

bookingReputation
number
required

The customer's reputation score based on their booking behavior. Calculated by Restoo from attendance, cancellation, and no-show history.

Interpretation:

  • Negative values: poor reputation.
  • 0: no sufficient history (neutral).
  • Positive values: good reputation
Example:

0.85

bookingsCount
integer
required

Total number of bookings made by the customer

Required range: x >= 0
Example:

25

visitsCount
integer
required

Total number of completed visits by the customer

Required range: x >= 0
Example:

18

cancellationsCount
integer
required

Total number of cancellations made by the customer

Required range: x >= 0
Example:

3

noShowsCount
integer
required

Total number of no-shows by the customer

Required range: x >= 0
Example:

2

firstVisitAt
string<date-time> | null
required

The date and time of the customer's first visit in ISO 8601 format

Example:

"2023-05-10T20:00:00+02:00"

lastVisitAt
string<date-time> | null
required

The date and time of the customer's most recent visit in ISO 8601 format

Example:

"2025-03-15T21:30:00+02:00"

firstCancellationAt
string<date-time> | null
required

The date and time of the customer's first cancellation in ISO 8601 format

Example:

"2024-09-12T19:00:00+02:00"

nextVisitScheduledAt
string<date-time> | null
required

The date and time of the customer's next scheduled visit in ISO 8601 format

Example:

"2025-04-05T22:00:00+02:00"

tags
Tag · object[]
required

List of customer tags

uuid
string
required

The Customer UUID

Example:

"50b5571be67b477baa9dead4b290c555"

email
string<email> | null
required

The Customer's email address

Example:

"steve.jobs@restoo.me"

phone
string | null
required

The Customer's phone number in E.164 format

Example:

"+34600111222"

birthDate
string<date> | null
required

Date of birth of the Customer in ISO 8601 format (YYYY-MM-DD)

Example:

"1979-03-20"

postalCode
string | null
required

The Customer's postal code

Maximum string length: 12
Example:

"28045"

isVip
boolean
required

Indicates whether the Customer is marked as VIP

Example:

true

isBusiness
boolean
required

Indicates whether the Customer is associated with a business

Example:

false

language
enum<string>
required

The preferred language of the Customer, represented as an ISO 639-1 code

Available options:
es,
ca,
it,
en,
de,
fr,
pt,
eu
Example:

"en"

acceptsImportantAlerts
boolean
required

Indicates whether the customer agrees to receive important alerts related to their bookings (e.g., cancellations due to weather or unexpected incidents)

Example:

true

Indicates whether the Customer has given GDPR consent

Example:

true

acceptsMarketing
boolean
required

Indicates whether the Customer has consented to receive marketing communications

Example:

true

country
enum<string>
required

The country represented as a two-letter ISO 3166-1 alpha-2 code

Available options:
AF,
AX,
AL,
DZ,
AS,
AD,
AO,
AI,
AQ,
AG,
AR,
AM,
AW,
AU,
AT,
AZ,
BS,
BH,
BD,
BB,
BY,
BE,
BZ,
BJ,
BM,
BT,
BO,
BQ,
BA,
BW,
BV,
BR,
IO,
BN,
BG,
BF,
BI,
CV,
KH,
CM,
CA,
KY,
CF,
TD,
CL,
CN,
CX,
CC,
CO,
KM,
CG,
CD,
CK,
CR,
CI,
HR,
CU,
CW,
CY,
CZ,
DK,
DJ,
DM,
DO,
EC,
EG,
SV,
GQ,
ER,
EE,
SZ,
ET,
FK,
FO,
FJ,
FI,
FR,
GF,
PF,
TF,
GA,
GM,
GE,
DE,
GH,
GI,
GR,
GL,
GD,
GP,
GU,
GT,
GG,
GN,
GW,
GY,
HT,
HM,
VA,
HN,
HK,
HU,
IS,
IN,
ID,
IR,
IQ,
IE,
IM,
IL,
IT,
JM,
JP,
JE,
JO,
KZ,
KE,
KI,
KP,
KR,
XK,
KW,
KG,
LA,
LV,
LB,
LS,
LR,
LY,
LI,
LT,
LU,
MO,
MG,
MW,
MY,
MV,
ML,
MT,
MH,
MQ,
MR,
MU,
YT,
MX,
FM,
MD,
MC,
MN,
ME,
MS,
MA,
MZ,
MM,
NA,
NR,
NP,
NL,
NC,
NZ,
NI,
NE,
NG,
NU,
NF,
MK,
MP,
NO,
OM,
PK,
PW,
PS,
PA,
PG,
PY,
PE,
PH,
PN,
PL,
PT,
PR,
QA,
RE,
RO,
RU,
RW,
BL,
SH,
KN,
LC,
MF,
PM,
VC,
WS,
SM,
ST,
SA,
SN,
RS,
SC,
SL,
SG,
SX,
SK,
SI,
SB,
SO,
ZA,
GS,
SS,
ES,
LK,
SD,
SR,
SJ,
SE,
CH,
SY,
TW,
TJ,
TZ,
TH,
TL,
TG,
TK,
TO,
TT,
TN,
TR,
TM,
TC,
TV,
UG,
UA,
AE,
GB,
UM,
US,
UY,
UZ,
VU,
VE,
VN,
VG,
VI,
WF,
EH,
YE,
ZM,
ZW
Example:

"ES"

name
string
required

The full name of the Customer

Required string length: 3 - 255
Example:

"Steve Jobs"