Update an ACS User

PATCH /acs/users/update ⇒ void

Updates the properties of a specified ACS user.

JavaScript

Request

await seam.acs.users.update({
  acs_user_id: "8d7e0b3a-b889-49a7-9164-4b71a0506a33",
  phone_number: 12222222222,
});

Response

// void

Python

Request

seam.acs.users.update(
    acs_user_id="8d7e0b3a-b889-49a7-9164-4b71a0506a33", phone_number=12222222222
)

Response

None

Ruby

Request

seam.acs.users.update(acs_user_id: "8d7e0b3a-b889-49a7-9164-4b71a0506a33", phone_number: 12222222222)

Response

nil

PHP

Request

<?php
$seam->acs->users->update(
    acs_user_id: "8d7e0b3a-b889-49a7-9164-4b71a0506a33",
    phone_number: 12222222222
);

Response

null

Seam CLI

Request

seam acs users update --acs_user_id "8d7e0b3a-b889-49a7-9164-4b71a0506a33" --phone_number 12222222222

Response

{}

Go

Request

package main

import api "github.com/seamapi/go"
import users "github.com/seamapi/go/users"

func main() {
	client.Acs.Users.Update(
		context.Background(),
		users.UsersUpdateRequest{
			AcsUserId:   api.String("8d7e0b3a-b889-49a7-9164-4b71a0506a33"),
			PhoneNumber: api.Float64(12222222222),
		},
	)
}

Response

nil

Request Parameters

access_schedule

Type: object Required: No

starts_at and ends_at timestamps for the acs_user's access. If you specify an access_schedule, you must include both starts_at and ends_at. ends_at must be a time in the future and after starts_at. Only applicable to Salto KS access control systems.

---

acs_user_id

Type: string Required: Yes

ID of the acs_user.

---

email

Type: string Required: No

---

email_address

Type: string Required: No

Email address of the acs_user.

---

full_name

Type: string Required: No

Full name of the acs_user.

---

hid_acs_system_id

Type: string Required: No

---

phone_number

Type: string Required: No

Phone number of the acs_user in E.164 format (for example, [phone]).

---

Return Type

void