Update a user’s first name, last name, or booking slug — useful when correcting a typo or rebranding a user’s public booking URL.Documentation Index
Fetch the complete documentation index at: https://developer.meetergo.com/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Request Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <your-api-key> |
Content-Type | Yes | application/json |
Request Body
All fields are optional. Provide only the fields you want to change — omitted fields stay unchanged.| Field | Type | Description |
|---|---|---|
givenName | string | First name |
familyName | string | Last name |
slug | string | Public booking slug. Min 5 characters; must be unique across the platform. Invalid characters are normalized automatically (e.g. "John Doe" → "john-doe"). |
Email is not editable here. Email changes affect the user’s login identity and require a separate flow. Contact support if you need to change a user’s email.
Examples
Fix a Typo in the Name
Change the Booking Slug
Response
Success (200 OK)
Returns the full updated user object.Error Responses
400 Bad Request — Empty Body
400 Bad Request — Slug Too Short
400 Bad Request — Slug Already Taken
403 Forbidden — Non-Admin Updating Someone Else
404 Not Found — User Outside Your Company
Notes
- Database-only update. This endpoint does not modify the user’s authentication identity (Cognito); it only updates the meetergo profile.
- Authorization. Any authenticated user can update their own profile. Only company admins can update other users in their company.
- Scoped to your company. You can only update users that belong to the same company as the caller.