Skip to main content
PATCH
Patch user on customer

Authorizations

Authorization
string
header
required

Authentication can be done by using a bearer token in the Authorization header. This is done using the following format Authorization: Bearer {token}.

Path Parameters

tenantId
string<uuid>
required

Id of the tenant the customer belongs to

customerId
string<uuid>
required

Id of the customer

userId
string<uuid>
required

Id of the user on the customer

Body

application/json

Patch user on customer body

contact
boolean

Whether the user is the contact person

lang
enum<string>

The language of the user

Available options:
bm,
ba,
eu,
be,
bn,
bh,
bi,
bs,
br,
bg,
my,
ca,
ch,
ce,
ny,
zh,
cv,
kw,
co,
cr,
hr,
cs,
da,
dv,
nl,
dz,
en,
eo,
et,
ee,
fo,
fj,
fi,
fr,
ff,
gl,
ka,
de,
el,
gn,
gu,
ht,
ha,
he,
hz,
hi,
ho,
hu,
ia,
id,
ie,
ga,
ig,
ik,
io,
is,
it,
iu,
ja,
jv,
kl,
kn,
kr,
ks,
kk,
km,
ki,
rw,
ky,
kv,
kg,
ko,
ku,
kj,
la,
lb,
lg,
li,
ln,
lo,
lt,
lu,
lv,
gv,
mk,
mg,
ms,
ml,
mt,
mi,
mr,
mh,
mn,
na,
nv,
nd,
ne,
ng,
nb,
nn,
no,
ii,
nr,
oc,
oj,
cu,
om,
or,
os,
pa,
pi,
fa,
pl,
ps,
pt,
qu,
rm,
rn,
ro,
ru,
sa,
sc,
sd,
se,
sm,
sg,
sr,
gd,
sn,
si,
sk,
sl,
so,
st,
es,
su,
sw,
ss,
sv,
ta,
te,
tg,
th,
ti,
bo,
tk,
tl,
tn,
to,
tr,
ts,
tt,
tw,
ty,
ug,
uk,
ur,
uz,
ve,
vi,
vo,
wa,
cy,
wo,
fy,
xh,
yi,
yo,
za,
zu
details
object

Response

Successful operation

The response is of type object.