Skip to main content
POST
/
v1
/
users
/
update
Update Users
curl --request POST \
  --url https://api.heymarket.com/v1/users/update \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "users": [
    {
      "id": 1,
      "first_name": "John",
      "last_name": "Doe"
    },
    {
      "id": 2,
      "role_id": 4
    }
  ]
}
'
{
  "memberships": [
    {
      "id": 1,
      "phone": "12345678900",
      "name": "John Doe",
      "email": "john.doe@email.com",
      "role_id": 1,
      "created_at": "2018-01-01T00:00:00Z",
      "updated_at": "2018-01-01T00:00:00Z",
      "user_created_at": "2018-01-01T00:00:00Z",
      "user_updated_at": "2018-01-01T00:00:00Z",
      "team_id": 1
    }
  ]
}
Use this endpoint to update one or more team users.

Authorizations

Authorization
string
header
required

Recommended authentication for new integrations. Generate a short-lived JWT from your API Secret ID and API Secret Key, then pass the signed JWT as a bearer token in the Authorization header.

API Secret credentials are available in the Heymarket app under Settings > Integrations > API. The Secret Key is shown only when it is generated, so copy and store it securely before closing the dialog.

Use the following JWT values:

{
"alg": "HS256",
"typ": "JWT"
}
{
"iss": "YOUR_API_SECRET_ID",
"iat": CURRENT_UNIX_TIMESTAMP
}

Replace CURRENT_UNIX_TIMESTAMP with the current Unix timestamp in seconds when generating the token.

Sign the JWT with HMAC-SHA256 using this signing secret:

YOUR_API_SECRET_ID||YOUR_API_SECRET_KEY

Send the signed JWT as a bearer token:

Authorization: Bearer YOUR_SIGNED_JWT

Tokens expire 5 minutes after the iat timestamp. Generate a new JWT per request, or cache it briefly for less than 5 minutes. Generate JWTs only from trusted server-side code; do not expose the API Secret Key in browser, mobile, or other client-side code.

Body

application/json

User fetch json

users
object[]

Response

Updated team user information

memberships
object[]