{
  "info": {
    "_postman_id": "d54e8beb-0ee0-483a-85b1-8e1001573149",
    "name": "Workvivo SCIM V2",
    "description": "This Postman collection provides endpoints for managing users within Workvivo.  \nIt supports creating, updating, retrieving, and deactivating user accounts.\n\n## Supported Resources\n\n- Users (`/scim/v2/Users`)\n    \n\n## Authentication\n\nAll endpoints require a Bearer token.\n\n## SCIM User Attributes\n\n**Schema:** `urn:ietf:params:scim:schemas:core:2.0:User`\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `id` | string | Server-generated Workvivo unique identifier (read-only) |\n| `userName` | string | Email address - match email.value (Mandatory) |\n| `externalId` | string | Unique identifier provided per user that will anchor user information for provisioning (Mandatory) |\n| `emails.value` | string | Email address - match userName value (Mandatory) |\n| `active` | boolean | Indicates whether the user is enabled (Yes/No) |\n\n---\n\n### Name\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `name.givenName` | string | First (given) name (Mandatory) |\n| `name.familyName` | string | Last (family) name (Mandatory) |\n| `displayName` | string | Display name |\n\n---\n\n### Email\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `emails.value` | string | Email address (Mandatory) |\n| `userName` | string | Email address - match email.value (Mandatory) |\n\n---\n\n### Phone Numbers\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `phoneNumbers.value` | string | Phone number |\n| `phoneNumbers.type` | string | work, mobile |\n\n---\n\n### Job Title\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `title` | string | Users Job Title |\n\n---\n\n### Address\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `locality` | string | Location (Secondary Team) |\n\n---\n\n## Enterprise User Attributes\n\n**Schema:** `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`\n\n### Team Data\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `department` | string | Department name(Primary Team) |\n| `costCenter` | string | Cost center (Tertiary Team) |\n| `Addtional taxonomies` | string | Additional Team types |\n\n---\n\n### Manager Data\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `manager.value` | string | SCIM ID of the user's manager |\n\n---\n\n### Hire Date\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `hireDate` | dateTime | Users Hire Date - Format YYYY-MM-DD |\n\n---\n\n### Date of Birth\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `dateOfBirth` | dateTime | Users Date of Birth - Format YYYY-MM-DD |\n\n---\n\n### Custom Field\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `CustomField` | string | Additional Custom Fields to the 'Other Information' |\n\n---\n\n## Filtering & Query Parameters\n\n| Parameter | Description |\n| --- | --- |\n| `filter` | SCIM filter expression (e.g., `userName eq \"jdoe\"`) |\n| `startIndex` | Pagination start index |\n| `count` | Number of results per page |\n| `sortBy` | Attribute to sort results by |\n| `sortOrder` | `asc` or `desc` |\n\n---",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json",
    "_exporter_id": "35392706",
    "_collection_link": "https://go.postman.co/collection/35392706-d54e8beb-0ee0-483a-85b1-8e1001573149?source=collection_link"
  },
  "item": [
    {
      "name": "SCIM Postman",
      "item": [
        {
          "name": "GET",
          "item": [
            {
              "name": "GET Users Collection",
              "request": {
                "auth": {
                  "type": "bearer",
                  "bearer": [
                    {
                      "key": "token",
                      "value": "",
                      "type": "string"
                    }
                  ]
                },
                "method": "GET",
                "header": [],
                "url": {
                  "raw": "{{baseURL}}/Users",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ]
                },
                "description": "# Get Users\n\n## What This Endpoint Does\n\nFetches user resources from the SCIM provider, returning user profile information including usernames, emails, names, and other attributes defined in the SCIM User schema.\n\n## Expected Response Format\n\nThe response follows the SCIM ListResponse schema:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n  \"totalResults\": 100,\n  \"startIndex\": 1,\n  \"itemsPerPage\": 50,\n  \"Resources\": [\n    {\n      \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n      \"id\": \"user-id\",\n      \"userName\": \"user@example.com\",\n      \"name\": {\n        \"givenName\": \"John\",\n        \"familyName\": \"Doe\"\n      },\n      \"emails\": [\n        {\n          \"value\": \"user@example.com\",\n          \"primary\": true\n        }\n      ],\n      \"active\": true\n    }\n  ]\n}\n\n ```\n\n## Common Use Cases\n\n- **User Synchronization**: Retrieve all users from Workvivo to sync with your identity provider\n    \n- **User Discovery**: List available users before performing specific operations\n    \n- **Audit & Reporting**: Export user data for compliance or reporting purposes\n    \n- **Pagination**: Use query parameters to paginate through large user lists\n    \n\n## Configuration Notes\n\n**`{{baseURL}}`** **Variable**: This variable must be configured in your environment to point to your Workvivo SCIM API endpoint.\n\nExample value: `https://your-instance.workvivo.com/scim/v2`\n\nMake sure to set this variable in your active environment before sending the request."
              },
              "response": []
            },
            {
              "name": "GET User - WorkvivoID",
              "protocolProfileBehavior": {
                "strictSSL": false
              },
              "request": {
                "method": "GET",
                "header": [],
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456",
                      "description": "(Required) Workvivo ID for the user."
                    }
                  ]
                },
                "description": "# Get User by Workvivo ID\n\n## What This Endpoint Does\n\nRetrieves a single user resource from the Workvivo SCIM API using their unique Workvivo ID. This endpoint returns the complete user profile including attributes such as username, email, name, active status, and any custom schema extensions.\n\n## Path Parameters\n\n| Parameter | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique Workvivo identifier for the user. This is the internal ID assigned to each user in the Workvivo system. |\n\n**Example:** `12345`\n\n## Authentication\n\nThis endpoint requires authentication using one of the following methods:\n\n- **Bearer Token**: Include your SCIM API token in the Authorization header\n    \n- **API Key**: Depending on your SCIM configuration\n    \n\n```\nAuthorization: Bearer {{api_token}}\n\n ```\n\nEnsure your API credentials have the appropriate permissions to read user resources.\n\n## Expected Response\n\n### Success Response (200 OK)\n\nReturns a SCIM User resource object containing:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"12345\",\n  \"userName\": \"user@example.com\",\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\",\n    \"formatted\": \"John Doe\"\n  },\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"active\": true,\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-01T00:00:00Z\",\n    \"lastModified\": \"2024-01-15T00:00:00Z\"\n  }\n}\n\n ```\n\n### Error Responses\n\n- **401 Unauthorized**: Invalid or missing authentication credentials\n     \n- **404 Not Found**: User with the specified WorkvivoID does not exist\n    \n- **429 Too Many Requests**: Rate limit exceeded\n    \n- **500 Internal Server Error**: Server-side error occurred\n    \n\n## Use Cases\n\n1. **User Profile Retrieval**: Fetch complete user details for display in administrative dashboards or user management interfaces\n    \n2. **Verification**: Confirm user existence and current status before performing operations\n    \n3. **Synchronization**: Retrieve the latest user data to sync with external identity providers or HR systems\n    \n4. **Audit & Compliance**: Access user information for audit trails and compliance reporting\n    \n5. **Integration Testing**: Validate SCIM implementation by retrieving known user records"
              },
              "response": []
            },
            {
              "name": "GET User Filter Email",
              "request": {
                "method": "GET",
                "header": [],
                "url": {
                  "raw": "{{baseURL}}/Users?filter=userName eq \"JoeBloggs@workvivio.com\"",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ],
                  "query": [
                    {
                      "key": "filter",
                      "value": "userName eq \"JoeBloggs@workvivio.com\"",
                      "description": "(Required) The user's email saved in Workvivo"
                    }
                  ]
                },
                "description": "# Get User by Email Filter\n\n## What This Endpoint Does\n\nThis request retrieves user information from the SCIM API by filtering on the `userName` attribute, which typically contains the user's email address. This operation allows you to search for a specific user in the identity management system.\n\n## Filter Parameter Syntax\n\nThe filter uses SCIM filtering syntax:\n\n```\nfilter=userName eq \"JoeBloggs@workvivio.com\"\n\n ```\n\n### Filter Components:\n\n- **Attribute**: `userName` - The user attribute to filter on\n    \n- **Operator**: `eq` - Equality operator (exact match)\n    \n- **Value**: `\"JoeBloggs@workvivio.com\"` - The email address to search for (must be in quotes)\n    \n\n## Expected Response Format\n\n### Success Response (200 OK):\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n  \"totalResults\": 1,\n  \"Resources\": [\n    {\n      \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n      \"id\": \"unique-user-id\",\n      \"userName\": \"JoeBloggs@workvivio.com\",\n      \"name\": {\n        \"givenName\": \"Joe\",\n        \"familyName\": \"Bloggs\"\n      },\n      \"emails\": [\n        {\n          \"value\": \"JoeBloggs@workvivio.com\",\n          \"primary\": true\n        }\n      ],\n      \"active\": true,\n      \"meta\": {\n        \"resourceType\": \"User\",\n        \"created\": \"2024-01-01T00:00:00Z\",\n        \"lastModified\": \"2024-01-01T00:00:00Z\"\n      }\n    }\n  ]\n}\n\n ```\n\n### No Results Found (200 OK):\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n  \"totalResults\": 0,\n  \"Resources\": []\n}\n\n ```\n\n### Error Response (400 Bad Request):\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:Error\"],\n  \"status\": \"400\",\n  \"detail\": \"Invalid filter syntax\"\n}\n\n ```\n\n## Use Cases\n\n- Verify if a user exists in the system before provisioning\n    \n- Retrieve user details for authentication or authorization\n    \n- Check user status and attributes\n    \n- Validate email addresses in the identity system"
              },
              "response": []
            },
            {
              "name": "GET User Filter ExternalID",
              "request": {
                "method": "GET",
                "header": [],
                "url": {
                  "raw": "{{baseURL}}/Users?filter=externalId eq \"123456\"",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ],
                  "query": [
                    {
                      "key": "filter",
                      "value": "externalId eq \"123456\"",
                      "description": "(Required) The external ID saved for the user in Workvivo."
                    }
                  ]
                },
                "description": "# Filter Users by External ID\n\n## What This Endpoint Does\n\nThis endpoint retrieves users from the SCIM directory by filtering on the `externalId` attribute. The `externalId` is a unique identifier assigned by the external identity provider or provisioning system, making it ideal for correlating users across different systems.\n\n## Filter Parameter\n\nThe `filter` query parameter uses SCIM filter syntax to search for users matching specific criteria.\n\n**Syntax:**\n\n```\nfilter=externalId eq \"value\"\n\n ```\n\n- **Attribute:** `externalId` - A string identifier for the resource as defined by the provisioning client\n    \n- **Operator:** `eq` (equals) - Performs an exact match comparison\n    \n- **Value:** Must be enclosed in double quotes\n    \n\n## Expected Response Format\n\nA successful request returns a SCIM `ListResponse` containing matching users:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n  \"totalResults\": 1,\n  \"Resources\": [\n    {\n      \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n      \"id\": \"internal-user-id\",\n      \"externalId\": \"123456\",\n      \"userName\": \"user@example.com\",\n      \"name\": {\n        \"givenName\": \"John\",\n        \"familyName\": \"Doe\"\n      },\n      \"emails\": [\n        {\n          \"value\": \"user@example.com\",\n          \"primary\": true\n        }\n      ],\n      \"active\": true,\n      \"meta\": {\n        \"resourceType\": \"User\",\n        \"created\": \"2024-01-01T00:00:00Z\",\n        \"lastModified\": \"2024-01-01T00:00:00Z\",\n        \"location\": \"{{baseURL}}/Users/internal-user-id\"\n      }\n    }\n  ],\n  \"startIndex\": 1,\n  \"itemsPerPage\": 1\n}\n\n ```\n\n**Response Fields:**\n\n- `totalResults` - Number of users matching the filter\n    \n- `Resources` - Array of matching user objects\n    \n- `startIndex` - The 1-based index of the first result\n    \n- `itemsPerPage` - Number of results returned per page\n    \n\n## Error Responses\n\n- **400 Bad Request** - Invalid filter syntax\n    \n- **401 Unauthorized** - Missing or invalid authentication\n    \n- **404 Not Found** - No users found matching the filter (some implementations)\n    \n- **500 Internal Server Error** - Server-side error processing the request\n    \n\n## Use Cases\n\n- Verify if a user exists in the system before provisioning\n    \n- Retrieve user details for authentication or authorization\n    \n- Check user status and attributes\n    \n- Validate email addresses in the identity system"
              },
              "response": []
            },
            {
              "name": "GET User Filter pagination",
              "request": {
                "method": "GET",
                "header": [],
                "url": {
                  "raw": "{{baseURL}}/Users?count=10&startIndex=11",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ],
                  "query": [
                    {
                      "key": "count",
                      "value": "10"
                    },
                    {
                      "key": "startIndex",
                      "value": "11"
                    }
                  ]
                },
                "description": "# GET User Filter Pagination\n\n## What This Endpoint Does\n\nThis endpoint retrieves a paginated list of users using the SCIM (System for Cross-domain Identity Management) protocol. It allows you to fetch user resources in manageable chunks rather than retrieving all users at once.\n\n## Query Parameters\n\n| Parameter | Value | Description |\n| --- | --- | --- |\n| `count` | `10` | Specifies the maximum number of user resources to return per page. This controls the page size. |\n| `startIndex` | `11` | Specifies the 1-based index of the first result to return. Used for pagination offset (e.g., startIndex=11 returns results starting from the 11th user). |\n\n## Expected Response Format\n\nThe response will be a JSON object following the SCIM ListResponse schema:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:ListResponse\"],\n  \"totalResults\": 100,\n  \"startIndex\": 11,\n  \"itemsPerPage\": 10,\n  \"Resources\": [\n    {\n      \"id\": \"user-id\",\n      \"userName\": \"user@example.com\",\n      \"name\": {\n        \"givenName\": \"John\",\n        \"familyName\": \"Doe\"\n      },\n      \"emails\": [...],\n      \"active\": true\n    }\n  ]\n}\n\n ```\n\n## Common Use Cases\n\n- **Iterating through large user datasets**: When you need to process all users but want to avoid memory issues or timeouts\n    \n- **Building paginated UI**: Displaying users in a table or list with page navigation\n    \n- **Incremental synchronization**: Fetching users in batches for syncing with external systems\n    \n- **Performance optimization**: Reducing response payload size and improving API response times\n    \n\n## Pagination Example\n\nTo retrieve all users, increment `startIndex` by `count` for each subsequent request:\n\n- Page 1: `startIndex=1&count=10` (users 1-10)\n    \n- Page 2: `startIndex=11&count=10` (users 11-20)\n    \n- Page 3: `startIndex=21&count=10` (users 21-30)\n    \n\nContinue until `startIndex` exceeds `totalResults` from the response."
              },
              "response": []
            }
          ]
        },
        {
          "name": "POST",
          "item": [
            {
              "name": "POST EXAMPLE",
              "request": {
                "method": "POST",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:schemas:core:2.0:User\",\n        \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\"\n    ],\n    \"externalId\": \"8715\",\n    \"userName\": \"joe.bloggs@workvivo.com\",\n    \"displayName\": \"Joe Bloggs\",\n    \"name\": {\n        \"formatted\": \"Joe Bloggs\",\n        \"familyName\": \"Joe\",\n        \"givenName\": \"Bloggs\"\n    },\n    \"emails\": [\n        {\n            \"type\": \"work\",\n            \"value\": \"joe.bloggs@workvivo.com\",\n            \"primary\": true\n        }\n    ],\n    \"phoneNumbers\": [\n        {\n            \"primary\": true,\n            \"type\": \"work\",\n            \"value\": \"1234567\"\n        },\n        {\n            \"primary\": true,\n            \"type\": \"mobile\",\n            \"value\": \"+1234567\"\n        }\n    ],\n    \"addresses\": [\n        {\n            \"locality\": \"Ireland\", // Secondary Team\n            \"type\": \"work\"\n        }\n    ],\n    \"title\": \"Technical Support\",\n    \"active\": true,\n    \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\": {\n        \"department\": \"Customer Support\", // Primary Team\n        \"hireDate\": \"2018-04-07T23:00:00Z\",\n        \"dateOfBirth\": \"1992-01-01T00:00:00Z\",\n        \"costCenter\": \"Operations\", // Tertiary Team\n        \"manager\": {\n            \"displayName\": \"\",\n            \"value\": \"654321\",\n            \"$ref\": \"\"\n        },\n        \"taxonomies\": [ // Additional Teams\n            {\n                \"displayName\": \"Customer Experience\",\n                \"type\": \"Division\"\n            },\n            {\n                \"displayName\": \"Workvivo\",\n                \"type\": \"Company\"\n            }\n        ]\n    }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ]
                },
                "description": "# Create SCIM User\n\n## What This Endpoint Does\n\nThis endpoint creates a new user in the system using the SCIM. SCIM provides a standardized way to manage user identities across different systems and applications.\n\n## Authentication\n\nThis endpoint requires authentication using a **Bearer token** or **API key** in the Authorization header:\n\n```\nAuthorization: Bearer {{api_token}}\n\n ```\n\nEnsure you have the necessary permissions to create users in the target system.\n\n## Request Body Schema\n\nThe request body must conform to the SCIM User schema. Below are the key fields:\n\n### Core Fields\n\n| Field | Type | Required | Description |\n| --- | --- | --- | --- |\n| `schemas` | Array | Yes | SCIM schema URIs. Must include `urn:ietf:params:scim:schemas:core:2.0:User` and optionally `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User` for enterprise attributes |\n| `externalId` | String | No | Unique identifier from the external system (e.g., employee ID) |\n| `userName` | String | Yes | Unique username, typically an email address |\n| `displayName` | String | No | The user's full display name |\n| `active` | Boolean | No | Whether the user account is active (true/false) (default: true) |\n\n### Name Object\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `formatted` | String | Full formatted name |\n| `familyName` | String | Last name/surname |\n| `givenName` | String | First name |\n\n### Emails Array\n\nArray of email objects with the following properties:\n\n- `value`: Email address\n    \n- `type`: Email type (e.g., \"work\", \"personal\")\n    \n- `primary`: Boolean indicating if this is the primary email\n    \n\n### Phone Numbers Array\n\nArray of phone number objects:\n\n- `value`: Phone number\n    \n- `type`: Phone type (e.g., \"work\", \"mobile\")\n    \n- `primary`: Boolean indicating if this is the primary number\n    \n\n### Addresses Array\n\nArray of address objects:\n\n- `locality`: City or region\n    \n- `type`: Address type (e.g., \"work\", \"home\")\n    \n\n### Additional Fields\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `title` | String | Job title or position |\n\n### Enterprise Extension Fields\n\nWhen using the enterprise extension schema (`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`), the following fields are available:\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `department` | String | Department name |\n| `hireDate` | String (ISO 8601) | Employee hire date |\n| `dateOfBirth` | String (ISO 8601) | Date of birth |\n| `Gender` | String | Gender identity |\n| `manager` | Object | Manager information with `displayName`, `value` (manager ID), and `$ref` (reference URL) |\n| `taxonomies` | Array | Organizational taxonomies with `displayName` and `type` (e.g., Division, Company) |\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| `201 Created` | User successfully created. Response includes the created user object with system-generated `id` and `meta` fields |\n| `400 Bad Request` | Invalid request body, missing required fields, or schema validation errors |\n| `401 Unauthorized` | Missing or invalid authentication credentials |\n| `409 Conflict` | User with the same `userName` or `externalId` already exists |\n| `500 Internal Server Error` | Server-side error during user creation |\n\n## Example Use Case\n\n**Scenario**: Onboarding a new employee to Workvivo\n\nWhen a new employee joins the organization, the HR system can automatically provision their Workvivo account by sending a POST request to this endpoint. The request includes:\n\n- Basic identity information (name, email, username)\n    \n- Contact details (work phone, mobile)\n    \n- Organizational data (department, hire date, manager)\n    \n- Company structure (division, company taxonomies)\n    \n\nThis automated provisioning ensures the new employee has immediate access to Workvivo with their profile pre-populated, reducing manual setup time and improving the onboarding experience.\n\n## Notes\n\n- The `userName` field is typically unique and often matches the primary email address\n    \n- Enterprise extension fields are optional but recommended for complete user profiles"
              },
              "response": []
            },
            {
              "name": "POST EXAMPLE - Minimum Fields required",
              "request": {
                "method": "POST",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:schemas:core:2.0:User\",\n        \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\"\n    ],\n    \"externalId\": \"87152\",\n    \"userName\": \"joe.bloggs@workvivo.com\",\n    \"name\": {\n        \"familyName\": \"Joe\",\n        \"givenName\": \"Bloggs\"\n    },\n    \"emails\": [\n        {\n            \"type\": \"work\",\n            \"value\": \"joe.bloggs@workvivo.com\",\n            \"primary\": true\n        }\n    ],\n    \"active\": true\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users"
                  ]
                },
                "description": "# Create SCIM User\n\n## What This Endpoint Does\n\nThis endpoint creates a new user in the system using the SCIM . SCIM provides a standardized way to manage user identities across different systems and applications.\n\nThe minimum attributes required are ExternalID, FirstName, LastName, Username/Email\n\n## Authentication\n\nThis endpoint requires authentication using a **Bearer token** or **API key** in the Authorization header:\n\n```\nAuthorization: Bearer {{api_token}}\n\n ```\n\nEnsure you have the necessary permissions to create users in the target system.\n\n## Request Body Schema\n\nThe request body must conform to the SCIM User schema. Below are the key fields:\n\n### Core Fields\n\n| Field | Type | Required | Description |\n| --- | --- | --- | --- |\n| `schemas` | Array | Yes | SCIM schema URIs. Must include `urn:ietf:params:scim:schemas:core:2.0:User` and optionally `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User` for enterprise attributes |\n| `externalId` | String | No | Unique identifier from the external system (e.g., employee ID) |\n| `userName` | String | Yes | Unique username, typically an email address |\n| `active` | Boolean | No | Whether the user account is active (true/false) (default: true) |\n\n### Name Object\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `familyName` | String | Last name/surname |\n| `givenName` | String | First name |\n\n### Emails Array\n\nArray of email objects with the following properties:\n\n- `value`: Email address\n    \n- `type`: Email type (e.g., \"work\", \"personal\")\n    \n- `primary`: Boolean indicating if this is the primary email\n    \n\n### ditional Fields\n\n|  |  |  |\n| --- | --- | --- |\n|  |  |  |\n\n### Enterprise Extension Fields\n\nWhen using the enterprise extension schema (`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`), the following fields are available:\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `department` | String | Department name |\n| `hireDate` | String (ISO 8601) | Employee hire date |\n| `dateOfBirth` | String (ISO 8601) | Date of birth |\n| `Gender` | String | Gender identity |\n| `manager` | Object | Manager information with `displayName`, `value` (manager ID), and `$ref` (reference URL) |\n| `taxonomies` | Array | Organizational taxonomies with `displayName` and `type` (e.g., Division, Company) |\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| `201 Created` | User successfully created. Response includes the created user object with system-generated `id` and `meta` fields |\n| `400 Bad Request` | Invalid request body, missing required fields, or schema validation errors |\n| `401 Unauthorized` | Missing or invalid authentication credentials |\n| `409 Conflict` | User with the same `userName` or `externalId` already exists |\n| `500 Internal Server Error` | Server-side error during user creation |\n\n## Example Use Case\n\n**Scenario**: Onboarding a new employee to Workvivo\n\nWhen a new employee joins the organization, the HR system can automatically provision their Workvivo account by sending a POST request to this endpoint. The request includes:\n\n- Basic identity information (name, email, username)\n    \n\nThis automated provisioning ensures the new employee has immediate access to Workvivo with their profile pre-populated, reducing manual setup time and improving the onboarding experience.\n\n## Notes\n\n- The `userName` field is typically unique and often matches the primary email address"
              },
              "response": []
            }
          ]
        },
        {
          "name": "PATCH",
          "item": [
            {
              "name": "Patch Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n{\n            \"op\": \"Replace\",\n            \"path\": \"active\",\n            \"value\": \"False\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Deactivate User via SCIM\n\n## What This Endpoint Does\n\nThis endpoint deactivates a user in Workvivo using the SCIM. When a user is deactivated, their `active` status is set to `false`, which typically prevents them from accessing the Workvivo platform while preserving their user data.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation.\n\n### Structure\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"active\",\n      \"value\": \"False\"\n    }\n  ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"active\"` to target the user's active status\n        \n    - **value** (string/boolean, required): The new value. Use `\"False\"` or `false` to deactivate the user\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false` |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct  |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Notes\n\n- Deactivating a user does not delete their account; it only prevents access\n    \n- To reactivate a user, send another PATCH request with `\"value\": \"True\"`\n    \n- Some organizations may have additional workflows triggered when a user is deactivated\n    \n- The PATCH operation can be used to modify other user attributes by changing the `path` and `value` fields\n    \n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch Full Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"name.familyName\",\n            \"value\": \"LAST_NAME\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"name.givenName\",\n            \"value\": \"FIRST_NAME\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"addresses[type eq \\\"work\\\"].locality\",\n            \"value\": \"LOCATION\"\n        },\n        {\n            \"op\": \"Add\",\n            \"path\": \"department\",\n            \"value\": \"DEPARTMENT\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:hireDate\",\n            \"value\": \"2019-04-07T23:00:00Z\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:dateOfBirth\",\n            \"value\": \"2008-04-07T23:00:00Z\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"title\",\n            \"value\": \"NEW JOB TITLE\"\n        },\n        {\n            \"op\": \"Replace\",\n            \"path\": \"manager\",\n            \"value\": \"WORKVIVO_ID\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User Information Full example\n\n## What This Endpoint Does\n\nThis endpoint updates user information in Workvivo using the SCIM . It allows you to modify specific user attributes without replacing the entire user resource.\n\n## Path Variable\n\n- **WorkvivoID** (required): The unique identifier for the user in Workvivo. This is the user's Workvivo ID that you want to update.\n    - Example: `123456`\n        \n\n## Request Body Structure\n\nThe request body follows the SCIM PatchOp schema and contains:\n\n- **schemas**: Array containing the PATCH operation schema identifier\n    \n    - Value: `[\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"]`\n        \n- **Operations**: Array of operation objects that define the changes to apply\n    \n\n### Operation Types\n\nEach operation in the `Operations` array contains:\n\n- **op**: The operation type (`Replace`, `Add`)\n    \n- **path**: The attribute path to modify (supports dot notation and filters)\n    \n- **value**: The new value to set\n    \n\n## Supported Operations in This Example\n\n### 1\\. Replace Name Fields\n\nUpdate the user's first and last name:\n\n``` json\n{\"op\": \"Replace\", \"path\": \"name.familyName\", \"value\": \"LAST_NAME\"}\n{\"op\": \"Replace\", \"path\": \"name.givenName\", \"value\": \"FIRST_NAME\"}\n\n ```\n\n### 2\\. Replace Work Address Locality\n\nUpdate the user's work location using a filtered path:\n\n``` json\n{\"op\": \"Replace\", \"path\": \"addresses[type eq \\\"work\\\"].locality\", \"value\": \"LOCATION\"}\n\n ```\n\n### 3\\. Add Department\n\nAdd or update the user's department:\n\n``` json\n{\"op\": \"Add\", \"path\": \"department\", \"value\": \"DEPARTMENT\"}\n\n ```\n\n### 4\\. Replace Enterprise Extension Fields\n\nUpdate custom enterprise schema attributes (dates):\n\n``` json\n{\"op\": \"Replace\", \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:startDate\", \"value\": \"2019-04-07T23:00:00Z\"}\n{\"op\": \"Replace\", \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:hireDate\", \"value\": \"2008-04-07T23:00:00Z\"}\n\n ```\n\n### 5\\. Replace Job Title\n\nUpdate the user's job title:\n\n``` json\n{\"op\": \"Replace\", \"path\": \"title\", \"value\": \"NEW JOB TITLE\"}\n\n ```\n\n### 6\\. Replace Manager\n\nUpdate the user's manager reference:\n\n``` json\n{\"op\": \"Replace\", \"path\": \"manager\", \"value\": \"WORKVIVO_ID\"}\n\n ```\n\n## Expected Response\n\nOn success, the endpoint returns:\n\n- **Status Code**: `200 OK`\n    \n- **Body**: The updated user resource with all modified attributes reflected\n    \n\nOn error, the endpoint may return:\n\n- **400 Bad Request**: Invalid PATCH operation syntax or unsupported path\n    \n- **404 Not Found**: User with specified WorkvivoID does not exist\n    \n- **401 Unauthorized**: Missing or invalid authentication credentials\n    \n\n## Notes\n\n- All operations in the `Operations` array are applied atomically\n    \n- The `Add` operation will create the attribute if it doesn't exist, or replace it if it does\n    \n- Path filters use SCIM filter syntax (e.g., `[type eq \"work\"]`)"
              },
              "response": []
            },
            {
              "name": "Patch Active Status Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"active\",\n            \"value\": \"True\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Deactivate User via SCIM\n\n## What This Endpoint Does\n\nThis endpoint deactivates a user in Workvivo using the SCIM. When a user is deactivated, their `active` status is set to `false`, which typically prevents them from accessing the Workvivo platform while preserving their user data.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation.\n\n### Structure\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"active\",\n      \"value\": \"False\"\n    }\n  ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"active\"` to target the user's active status\n        \n    - **value** (string/boolean, required): The new value. Use `\"False\"` or `false` to deactivate the user\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false`  |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Notes\n\n- Deactivating a user does not delete their account; it only prevents access\n    \n- To reactivate a user, send another PATCH request with `\"value\": \"True\"`\n    \n- Some organizations may have additional workflows triggered when a user is deactivated\n    \n- The PATCH operation can be used to modify other user attributes by changing the `path` and `value` fields\n    \n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch Email Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"replace\",\n            \"path\": \"emails[type eq \\\"work\\\"].value\",\n            \"value\": \"new-email@test.com\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update Email via SCIM\n\n## What This Endpoint Does\n\nThis endpoint is used to update a users email in Workvivo using the SCIM.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation specification.\n\n### Structure\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"active\",\n      \"value\": \"False\"\n    }\n  ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"active\"` to target the user's active status\n        \n    - **value** (string/boolean, required): The new value. Use `\"False\"` or `false` to deactivate the user\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false` |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Notes\n\n- Deactivating a user does not delete their account; it only prevents access\n    \n- To reactivate a user, send another PATCH request with `\"value\": \"True\"`\n    \n- Some organizations may have additional workflows triggered when a user is deactivated\n    \n- The PATCH operation can be used to modify other user attributes by changing the `path` and `value` fields\n    \n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch First/LastName Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n     ],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"name.givenName\",\n      \"value\": \"John\"\n    },\n    {\n      \"op\": \"Replace\",\n      \"path\": \"name.familyName\",\n      \"value\": \"Doe\"\n    }\n  ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update FirstName or LastName via SCIM\n\n## What This Endpoint Does\n\nThis endpoint is used to update a users First or Last Name in Workvivo using the SCIM.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation.\n\n### Structure\n\n``` json\n{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n     ],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"name.givenName\",\n      \"value\": \"John\"\n    },\n    {\n      \"op\": \"Replace\",\n      \"path\": \"name.familyName\",\n      \"value\": \"Doe\"\n    }\n  ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"`name`\"` to target the user's name. Add the name vairable to target the users First or last name\n        \n    - **value** (string, required): The new name value. Use `\"name.givenName\"` to target the first name or `name.familyName` to target the users Last Name\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false` |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch DisplayName Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"displayName\",\n            \"value\": \"Joe Bloggs\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update DisplayName via SCIM\n\n## What This Endpoint Does\n\nThis endpoint is used to update a users Display Name in Workvivo using the SCIM.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation specification.\n\n### Structure\n\n``` json\n{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"displayName\",\n            \"value\": \"Joe Bloggs\"\n        }\n    ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"`displayName`\"` to target the user's displayName.\n        \n    - **value** (string, required): The new DisplayName value.\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false` |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"displayName\": \"John Doe\",\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch Job Title Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"add\",\n            \"path\": \"title\",\n            \"value\": \"New Job Title\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update Job Title via SCIM\n\n## What This Endpoint Does\n\nThis endpoint is used to update a users Job Title in Workvivo using the SCIM.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique identifier for the user in Workvivo. This is the SCIM user ID that was returned when the user was created or can be retrieved via the GET Users endpoint. |\n\n**Example:** `123456`\n\n## Request Body\n\nThe request body follows the SCIM PATCH operation.\n\n### Structure\n\n``` json\n{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"title\",\n            \"value\": \"HR Manager\"\n        }\n    ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (array, required): Array of operations to perform on the user resource\n    \n    - **op** (string, required): The operation type. Use `\"Replace\"` to update the active status\n        \n    - **path** (string, required): The attribute path to modify. Use `\"title\"` to target the user's Job Title.\n        \n    - **value** (string, required): The new Job Title value.\n        \n\n## Authentication\n\nThis endpoint requires authentication via the SCIM bearer token. Ensure your request includes:\n\n```\nAuthorization: Bearer {{your_scim_token}}\n\n ```\n\nThe SCIM token should be configured in your Workvivo admin settings and stored securely as an environment variable.\n\n## Response Codes\n\n| Status Code | Description |\n| --- | --- |\n| **200 OK** | User successfully deactivated. Returns the updated user resource with `active: false` |\n| **400 Bad Request** | Invalid request body or malformed PATCH operation. Check that the request follows SCIM PATCH specification |\n| **401 Unauthorized** | Missing or invalid authentication token. Verify your SCIM bearer token is correct |\n| **404 Not Found** | User with the specified WorkvivoID does not exist |\n| **409 Conflict** | User is already deactivated or there's a conflict with the current state |\n| **500 Internal Server Error** | Server error occurred. Contact Workvivo support if this persists |\n\n## Prerequisites\n\n1. **SCIM Integration Enabled**: SCIM must be enabled for your Workvivo organization\n    \n2. **Valid SCIM Token**: You must have a valid SCIM bearer token with user management permissions\n    \n3. **User Exists**: The user with the specified WorkvivoID must exist in Workvivo\n    \n\n## Example Success Response\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:schemas:core:2.0:User\"],\n  \"id\": \"123456\",\n  \"userName\": \"user@example.com\",\n  \"active\": false,\n  \"name\": {\n    \"givenName\": \"John\",\n    \"familyName\": \"Doe\"\n  },\n  \"displayName\": \"John Doe\",\n  \"emails\": [\n    {\n      \"value\": \"user@example.com\",\n      \"primary\": true\n    }\n  ],\n  \"title\": \"HR Manager\",\n  \"meta\": {\n    \"resourceType\": \"User\",\n    \"created\": \"2024-01-15T10:30:00Z\",\n    \"lastModified\": \"2024-01-20T14:45:00Z\",\n    \"location\": \"{{baseURL}}/Users/123456\"\n  }\n}\n\n ```\n\n## Related Endpoints\n\n- **GET /Users/:WorkvivoID** - Retrieve user details\n    \n- **PUT /Users/:WorkvivoID** - Update user (full replacement)"
              },
              "response": []
            },
            {
              "name": "Patch Manager Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager\",\n            \"value\": \"Manager Workvivo ID\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User's Manager\n\n## What This Endpoint Does\n\nThis endpoint updates a user's manager in Workvivo using the SCIM PATCH operation. It allows you to modify the manager relationship for a specific user by replacing the manager field with a new manager's Workvivo ID.\n\n## Path Variables\n\n| Variable | Type | Required | Description |\n| --- | --- | --- | --- |\n| `WorkvivoID` | string | Yes | The unique Workvivo ID of the user whose manager is being updated. Example: `123456` |\n\n## Request Body Structure\n\nThis endpoint uses the SCIM PATCH request format, which follows the specification.\n\n### Body Schema\n\n``` json\n{\n  \"schemas\": [\n    \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n  ],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager\",\n      \"value\": \"Manager Workvivo ID\"\n    }\n  ]\n}\n\n ```\n\n### Field Descriptions\n\n- **`schemas`** (array, required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **`Operations`** (array, required): An array of patch operations to perform. Each operation contains:\n    \n    - **`op`** (string, required): The operation type. Use `\"Replace\"` to update the manager field\n        \n    - **`path`** (string, required): The attribute path to modify. For manager updates, use `\"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager\"` which references the enterprise user extension schema\n        \n    - **`value`** (string, required): The new manager's Workvivo ID. This should be the unique identifier of the user who will become the manager\n        \n\n## Operation Details\n\n### Replace Operation\n\nThe `Replace` operation modifies the existing manager value for the specified user. If the user currently has a manager assigned, this operation will replace it with the new manager ID. If no manager is currently assigned, this operation will set the manager for the first time.\n\n### Manager Path\n\nThe path `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager` follows the SCIM Enterprise User Schema Extension, which is a standard extension for representing organizational information like manager relationships.\n\n## Example Usage\n\nTo update user `123456` to report to manager `789012`:\n\n``` json\n{\n  \"schemas\": [\n    \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n  ],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager\",\n      \"value\": \"789012\"\n    }\n  ]\n}\n\n ```\n\n## SCIM PATCH Notes\n\n- Multiple operations can be included in the `Operations` array to perform multiple updates in a single request\n    \n- The PATCH operation is atomic - either all operations succeed or all fail\n    \n- Supported operation types include: `Add`, and `Replace`\n    \n- The `path` attribute uses attribute notation as defined in SCIM, which can include schema URNs for extension attributes\n    \n- If the operation fails, the response will include error details following the SCIM error response format\n    \n\n## Response\n\nA successful PATCH operation typically returns:\n\n- **200 OK**: The user resource was successfully updated, with the updated user object in the response body\n    \n- Error responses follow standard SCIM error format with appropriate HTTP status codes (400, 401, 404, etc.)."
              },
              "response": []
            },
            {
              "name": "Patch Department(Primary Team) Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department\",\n            \"value\": \"VALUE\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User's Primary Department/Team\n\n## What This Endpoint Does\n\nThis endpoint uses the SCIM protocol to perform a partial update on a user profile. Specifically, it replaces the primary team of the users profile. It allows you to modify the users primary team without affecting other user attributes.\n\n## Endpoint Details\n\n**Method:** `PATCH`  \n**URL:** `{{baseURL}}/Users/:WorkvivoID`\n\n## Path Variables\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier of the user in Workvivo whose department/team information needs to be updated | `123456` |\n\n## Request Body\n\nThis endpoint uses the **SCIM PATCH** format.\n\n### Structure\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department\",\n      \"value\": \"VALUE\"\n    }\n  ]\n}\n\n ```\n\n### Fields\n\n- **schemas** (required): Must contain `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (required): An array of patch operations to perform on the user resource\n    \n\n### Operation Object\n\n- **op** (required): The operation type. Set to `\"Replace\"` to update the existing department value\n    \n- **path** (required): The attribute path to modify. Uses `\"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department\"` to target the department field in the SCIM Enterprise User extension\n    \n- **value** (required): The new department/team value to assign to the user. Replace `\"VALUE\"` with the actual department name or identifier\n    \n\n## What This Does\n\nThis request performs a **Replace** operation on a user's primary department/team assignment. The operation:\n\n1. Identifies the user by their `WorkvivoID`\n    \n2. Targets the `department` attribute within the SCIM Enterprise User schema extension\n    \n3. Replaces the current department value with the new value provided\n    \n\n## SCIM Protocol Notes\n\n- This endpoint follows the **SCIM 2.0** (System for Cross-domain Identity Management) specification\n    \n- The PATCH operation allows partial updates to user resources without requiring the entire user object\n    \n- The `department` field is part of the **Enterprise User Schema Extension** (`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`)\n    \n- Multiple operations can be included in the `Operations` array to update multiple attributes in a single request\n    \n- Supported operation types include: `Add` and `Replace`"
              },
              "response": []
            },
            {
              "name": "Patch Location(Secondary) Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"addresses[type eq \\\"work\\\"].locality\",\n            \"value\": \"VALUE\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User Work Location (Locality)\n\n## What This Endpoint Does\n\nThis endpoint uses the SCIM protocol to perform a partial update on a user profile. Specifically, it replaces the secondary team of the users profile. It allows you to modify the users secondary team without affecting other user attributes.\n\n## Path Variables\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier for the user in Workvivo whose work location you want to update | `123456` |\n\n## Request Body Structure\n\nThe request body follows the SCIM PATCH operation format:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"addresses[type eq \\\"work\\\"].locality\",\n      \"value\": \"VALUE\"\n    }\n  ]\n}\n\n ```\n\n### Body Parameters\n\n- **schemas** (required): Must include `urn:ietf:params:scim:api:messages:2.0:PatchOp` to indicate this is a SCIM PATCH operation\n    \n- **Operations** (required): An array of operation objects to be performed\n    \n\n### Operation Object\n\n- **op** (required): The operation type - `Replace` in this case, which updates the specified field\n    \n- **path** (required): The attribute path using SCIM filter notation\n    \n    - `addresses[type eq \"work\"].locality` targets the `locality` field of the address where `type` equals `\"work\"`\n        \n- **value** (required): The new value for the locality field (e.g., city name like \"Dublin\", \"New York\", \"London\")\n    \n\n## SCIM PATCH Operations\n\n### Supported Operations\n\n- **Add**: Adds a new attribute or value\n    \n- **Replace**: Updates an existing attribute value (used in this request)\n    \n- **Remove**: Deletes an attribute or value\n    \n\n### Path Filter Syntax\n\nThe path uses SCIM filter notation to target specific elements:\n\n- `addresses[type eq \"work\"]` - Filters the addresses array for entries where type equals \"work\"\n    \n- `.locality` - Targets the locality field within the filtered address\n    \n\n### Important Notes\n\n- PATCH operations are atomic - either all operations succeed or all fail\n    \n- The path filter is case-sensitive\n    \n- If the specified address doesn't exist, the operation may fail depending on server configuration\n    \n- Multiple operations can be included in the Operations array to update multiple fields in a single request\n    \n\n## Example Use Case\n\nUpdate a user's work location from \"San Francisco\" to \"Austin\":\n\n- Set `WorkvivoID` to the user's ID\n    \n- Set `value` to `\"Austin\"`"
              },
              "response": []
            },
            {
              "name": "Patch CostCenter(Tertiary) Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter\",\n            \"value\": \"VALUE\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User Cost Center (Tertiary)\n\n## What This Endpoint Does\n\nThis endpoint uses the SCIM protocol to perform a partial update on a user profile. Specifically, it replaces the tertiary team of the users profile. It allows you to modify the users tertiary team without affecting other user attributes.\n\n## Path Variable\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier for the user in Workvivo. This ID is used to target the specific user resource to be updated. | `123456` |\n\n## Request Body Structure\n\nThe request body follows the SCIM PATCH operation format.\n\n### Schema\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"]\n}\n\n ```\n\nThe `schemas` attribute identifies this as a SCIM PATCH operation request.\n\n### Operations Array\n\nThe `Operations` array contains one or more modification operations to apply to the user resource:\n\n``` json\n{\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter\",\n      \"value\": \"VALUE\"\n    }\n  ]\n}\n\n ```\n\n**Operation Properties:**\n\n- **`op`**: The operation type. In this example, `\"Replace\"` is used to update an existing value.\n    \n- **`path`**: The attribute path to modify. Uses the fully qualified schema URN followed by the attribute name (`costCenter`).\n    \n- **`value`**: The new value to set for the cost center field. Replace `\"VALUE\"` with the actual cost center identifier.\n    \n\n## SCIM Schema\n\nThis request uses the **SCIM Enterprise User Schema Extension**:\n\n- **Schema URN**: `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`\n    \n- **Attribute**: `costCenter` (also referred to as \"Tertiary\" in Workvivo's implementation)\n    \n\nThe Enterprise User Schema Extension is a standard SCIM extension that adds enterprise-specific attributes like employee number, cost center, organization, division, and manager.\n\n## Usage Notes\n\n1. **Authentication**: Ensure you have a valid bearer token or API key configured in the collection's authorization settings.\n    \n2. **Path Format**: The `path` attribute in the operation must use the fully qualified schema URN format when targeting extension attributes.\n    \n3. **Operation Types**: Besides `\"Replace\"`, SCIM PATCH supports:\n    \n    - `\"Add\"` - Add a new attribute or value\n        \n4. **Response**: A successful PATCH operation typically returns a `200 OK` status code. Some implementations may return the updated user resource.\n    \n\n## Example Values\n\nReplace `\"VALUE\"` in the request body with an actual cost center code, such as:\n\n- `\"Engineering-West\"`\n    \n- `\"DEPT-001\"`\n    \n\nThe format depends on your organization's cost center naming convention."
              },
              "response": []
            },
            {
              "name": "Patch Additional Taxonomies(Team Types) Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:customTaxonomies[value eq \\\"TEAM_TYPE\\\"]\",\n            \"value\": \"VALUE\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update Additional Taxonomies (Team Types)\n\n## What This Endpoint Does\n\nThis endpoint updates additional taxonomies, specifically team types, for a user in the Workvivo system using the SCIM PATCH operation.\n\n## Path Variable\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier for the user in Workvivo whose taxonomies you want to update | `123456` |\n\n## Request Body Structure\n\nThe request follows the SCIM PATCH operation specification:\n\n### Schemas\n\n``` json\n\"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"]\n\n ```\n\nThis declares that the request conforms to the SCIM PatchOp message schema, which is required for all PATCH operations in SCIM.\n\n### Operations Array\n\nThe `Operations` array contains one or more modification operations to be applied to the user resource. Each operation specifies:\n\n- **`op`**: The operation type (e.g., `Replace`, `Add`)\n    \n- **`path`**: The attribute path to modify using JSON path notation\n    \n- **`value`**: The new value to set for the specified path\n    \n\n## Replace Operation\n\nThis request uses the **Replace** operation to update existing taxonomy values:\n\n``` json\n{\n  \"op\": \"Replace\",\n  \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:taxonomies:teamTypes\",\n  \"value\": \"VALUE\"\n}\n\n ```\n\n### Path Explanation\n\nThe `path` field uses SCIM's attribute notation to target a specific nested attribute:\n\n- **`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`**: References the enterprise extension schema for user objects\n    \n- **`taxonomies`**: The taxonomies attribute within the extension\n    \n- **`teamTypes`**: The specific taxonomy type being updated (team types classification)\n    \n\nThis path structure allows you to precisely target the team types taxonomy without affecting other user attributes.\n\n## Use Cases\n\n- Updating a user's team classification when they change departments\n    \n- Modifying team type assignments during organizational restructuring\n    \n- Correcting or updating taxonomy metadata for user profiles\n    \n\n## Expected Response\n\nA successful PATCH operation typically returns:\n\n- **200 OK**: The user resource with updated attributes\n    \n\n## Notes\n\n- Multiple operations can be included in the `Operations` array to update multiple attributes in a single request\n    \n- The `Replace` operation will overwrite the existing value at the specified path\n    \n- Ensure the `value` provided matches the expected data type for the team types taxonomy"
              },
              "response": []
            },
            {
              "name": "Patch Custom Attributes Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Add\",\n            \"path\": \"Custom Field\",\n            \"value\": \"VALUE\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update Custom Attributes Example\n\n## What This Endpoint Does\n\nThis endpoint updates custom attributes for a user in Workvivo using the SCIM PATCH operation. Use this request to modify user custom attributes in Workvivo via SCIM.\n\n## HTTP Method\n\n**PATCH** - Partially updates a user resource\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier for the user in Workvivo whose custom attributes you want to update | `123456` |\n\n## Request Body Structure\n\nThe request body follows the SCIM PATCH operation schema:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Add\",\n      \"path\": \"Custom Field\",\n      \"value\": \"VALUE\"\n    }\n  ]\n}\n\n ```\n\n### Schema\n\n- **schemas**: Must include `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n\n### Operations Array\n\nThe `Operations` array contains one or more operation objects that define the changes to apply:\n\n| Field | Type | Description | Possible Values |\n| --- | --- | --- | --- |\n| `op` | String | The operation type to perform | `Add`, `Replace`, `Remove` |\n| `path` | String | The attribute path to modify (the name of the custom field) | Any custom field name configured in Workvivo |\n| `value` | String/Object | The value to set for the custom attribute | Any valid value for the custom field |\n\n## Example Usage\n\n### Adding a Custom Field\n\nTo add a value to a custom field named \"Department\":\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Add\",\n      \"path\": \"Department\",\n      \"value\": \"Engineering\"\n    }\n  ]\n}\n\n ```\n\n### Replacing a Custom Field\n\nTo update an existing custom field value:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"Department\",\n      \"value\": \"Product\"\n    }\n  ]\n}\n\n ```\n\n### Multiple Operations\n\nYou can perform multiple operations in a single request:\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Add\",\n      \"path\": \"Department\",\n      \"value\": \"Engineering\"\n    },\n    {\n      \"op\": \"Replace\",\n      \"path\": \"Location\",\n      \"value\": \"Dublin\"\n    }\n  ]\n}\n\n ```\n\n## Notes\n\n- Ensure the custom field name in the `path` matches exactly with the custom field configured in your Workvivo instance\n    \n- The `WorkvivoID` must be a valid user identifier in your Workvivo system\n    \n- Custom attributes must be pre-configured in Workvivo before they can be updated via SCIM"
              },
              "response": []
            },
            {
              "name": "Patch Date Of Birth Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:dateOfBirth\",\n            \"value\": \"YYYY-MM-DD\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User Date of Birth\n\n## What This Endpoint Does\n\nThis endpoint updates a user's date of birth using the PATCH operation. It allows you to modify the `dateOfBirth` field for a specific user in the Workvivo system through a standards-compliant SCIM request.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n## Path Variables\n\n| Variable | Description | Example |\n| --- | --- | --- |\n| `WorkvivoID` | The unique identifier for the user in Workvivo whose date of birth you want to update | `123456` |\n\n## Request Body Structure\n\nThe request follows the SCIM PATCH operation.\n\n### Schema\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [...]\n}\n\n ```\n\n- **schemas**: Must include `urn:ietf:params:scim:api:messages:2.0:PatchOp` to indicate this is a SCIM PATCH operation\n    \n- **Operations**: An array of operation objects that define the modifications to be made\n    \n\n### Operations Array\n\nEach operation object contains:\n\n| Field | Description | Value in this example |\n| --- | --- | --- |\n| `op` | The operation type | `Replace` - replaces the existing value |\n| `path` | The attribute path to modify using SCIM schema notation | `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:dateOfBirth` |\n| `value` | The new value to set | Date string in `YYYY-MM-DD` format |\n\n### PATCH Operation Details\n\nThis request performs a **Replace** operation on the date of birth field:\n\n- **Operation**: `Replace` - Replaces the current value of the specified attribute\n    \n- **Target Field**: `dateOfBirth` from the SCIM Enterprise User extension schema\n    \n- **Schema Path**: `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:dateOfBirth`\n    \n\n## Date Format\n\n⚠️ **Important**: The date of birth must be provided in **ISO 8601 date format**:\n\n- **Format**: `YYYY-MM-DD`\n    \n- **Example**: `1990-05-15`\n    \n- **Year**: 4-digit year\n    \n- **Month**: 2-digit month (01-12)\n    \n- **Day**: 2-digit day (01-31)\n    \n\n## SCIM PATCH Operation Notes\n\n- PATCH operations allow partial updates without replacing the entire resource\n    \n- Multiple operations can be included in the `Operations` array to update multiple fields in a single request\n    \n- The `Replace` operation will create the attribute if it doesn't exist, or update it if it does\n    \n- Other supported operation types include `Add`\n    \n- All PATCH requests must include the SCIM PatchOp schema in the `schemas` array\n    \n- The operation is atomic - either all operations succeed or none are applied\n    \n\n## Example Request Body\n\n``` json\n{\n  \"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"],\n  \"Operations\": [\n    {\n      \"op\": \"Replace\",\n      \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:dateOfBirth\",\n      \"value\": \"1985-03-22\"\n    }\n  ]\n}\n\n ```"
              },
              "response": []
            },
            {
              "name": "Patch HireDate Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Replace\",\n            \"path\": \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:hireDate\",\n            \"value\": \"YYYY-MM-DD\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User Hire Date\n\n## What This Endpoint Does\n\nThis endpoint updates a user's hire date in Workvivo using the PATCH operation. It allows you to modify the hire date attribute for an existing user without affecting other user properties.\n\n## Path Variable\n\n- **WorkvivoID** (required): The unique identifier for the user in Workvivo whose hire date you want to update. This should be the user's SCIM ID.\n    - Example: `123456`\n        \n\n## Request Body\n\nThe request uses the SCIM PATCH operation format, which consists of:\n\n### Schema\n\n- `schemas`: Must include `\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"` to indicate this is a SCIM PATCH operation\n    \n\n### Operations Array\n\nThe `Operations` array contains one or more patch operations to perform:\n\n- **op**: The operation type - use `\"Replace\"` to update the hire date value\n    \n- **path**: The attribute path to modify - `\"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:hireDate\"` targets the hire date field in the SCIM Enterprise User extension\n    \n- **value**: The new hire date value in **YYYY-MM-DD** format (e.g., `\"2024-01-15\"`)\n    \n\n## Date Format\n\n⚠️ **Important**: The hire date must be provided in ISO 8601 date format: `YYYY-MM-DD`\n\nExamples:\n\n- `\"2024-01-15\"`\n    \n\n## Usage Notes\n\n- This operation only updates the hire date field; other user attributes remain unchanged\n    \n- The PATCH operation is idempotent - sending the same request multiple times will produce the same result\n    \n- Ensure the WorkvivoID corresponds to an existing user in the system\n    \n- Multiple operations can be included in the Operations array to update multiple fields in a single request"
              },
              "response": []
            },
            {
              "name": "Patch Mobile/Phone Number Example",
              "request": {
                "method": "PATCH",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:api:messages:2.0:PatchOp\"\n    ],\n    \"Operations\": [\n        {\n            \"op\": \"Add\",\n            \"path\": \"phoneNumbers[type eq \\\"work\\\"].value\",\n            \"value\": \"--\"\n        },\n        {\n            \"op\": \"Add\",\n            \"path\": \"phoneNumbers[type eq \\\"mobile\\\"].value\",\n            \"value\": \"(416) 555-1212\"\n        }\n    ]\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update Mobile/Phone Number Example\n\n## What This Endpoint Does\n\nThis PATCH request updates user phone numbers using SCIM PATCH operations. It demonstrates how to add or update both work and mobile phone numbers for a specific user on the Workvivo system.\n\n## Endpoint\n\n```\nPATCH {{baseURL}}/Users/:WorkvivoID\n\n ```\n\n### Path Variables\n\n- **WorkvivoID** (required): The unique identifier for the user in Workvivo whose phone numbers you want to update.\n    \n    - Example: `123456`\n        \n    - This ID should correspond to an existing user in your Workvivo instance.\n        \n\n## Request Body Structure\n\nThe request body follows the SCIM PATCH operation specification:\n\n### Schemas\n\n``` json\n\"schemas\": [\"urn:ietf:params:scim:api:messages:2.0:PatchOp\"]\n\n ```\n\nThis declares that the request conforms to the SCIM PATCH operation message format.\n\n### Operations Array\n\nThe `Operations` array contains one or more PATCH operations to perform on the user resource:\n\n``` json\n\"Operations\": [\n  {\n    \"op\": \"Add\",\n    \"path\": \"phoneNumbers[type eq \\\"work\\\"].value\",\n    \"value\": \"--\"\n  },\n  {\n    \"op\": \"Add\",\n    \"path\": \"phoneNumbers[type eq \\\"mobile\\\"].value\",\n    \"value\": \"(416) 555-1212\"\n  }\n]\n\n ```\n\n#### Operation Fields:\n\n- **op**: The operation type. `\"Add\"` will create the phone number if it doesn't exist, or update it if it does.\n    \n- **path**: A SCIM path expression that targets the specific attribute to modify:\n    \n    - `phoneNumbers[type eq \"work\"].value` - Targets the work phone number\n        \n    - `phoneNumbers[type eq \"mobile\"].value` - Targets the mobile phone number\n        \n- **value**: The new phone number value to set\n    \n\n## Use Case\n\nThis example demonstrates updating multiple phone number types in a single PATCH request:\n\n- **Work phone**: Set to `\"987654321\"` (placeholder or to be removed)\n    \n- **Mobile phone**: Set to `\"(416) 555-1212\"`\n    \n\nYou can modify the values and add additional operations to update other phone number types or user attributes as needed."
              },
              "response": []
            }
          ]
        },
        {
          "name": "PUT",
          "item": [
            {
              "name": "PUT Example",
              "request": {
                "auth": {
                  "type": "bearer",
                  "bearer": [
                    {
                      "key": "token",
                      "value": "",
                      "type": "string"
                    }
                  ]
                },
                "method": "PUT",
                "header": [],
                "body": {
                  "mode": "raw",
                  "raw": "{\n    \"schemas\": [\n        \"urn:ietf:params:scim:schemas:core:2.0:User\",\n        \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\"\n    ],\n    \"externalId\": \"8752\",\n    \"userName\": \"Joe.bloggs2@workvivo.com\",\n    \"name\": {\n        \"formatted\": \"Joe Bloggs\",\n        \"familyName\": \"Bloggs\",\n        \"givenName\": \"Joe\"\n    },\n    \"emails\": [\n        {\n            \"type\": \"work\",\n            \"value\": \"Joe.bloggs2@workvivo.com\",\n            \"primary\": true\n        }\n    ],\n    \"phoneNumbers\": [\n        {\n            \"primary\": true,\n            \"type\": \"work\",\n            \"value\": \"3534353\"\n        },\n        {\n            \"primary\": true,\n            \"type\": \"mobile\",\n            \"value\": \"+354769999\"\n        }\n    ],\n    \"addresses\": [\n        {\n            \"locality\": \"Location Name\", // Secondary Team\n            \"type\": \"work\"\n        }\n    ],\n    \"title\": \"Job Title\",\n    \"active\": true,\n    \"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\": {\n        \"department\": \"Department\", // Primary Team\n        \"hireDate\": \"2018-04-07T23:00:00Z\",\n        \"dateOfBirth\": \"1977-01-01T00:00:00Z\",\n        \"costCenter\": \"Operations\", // Tertiary Team\n        \"manager\": {\n            \"displayName\": \"\",\n            \"value\": \"WORKVIVOID\",\n            \"$ref\": \"\"\n        },\n        \"taxonomies\": [  // Additional Teams\n            {\n                \"displayName\": \"Dv1\",\n                \"type\": \"Division\"\n            },\n            {\n                \"displayName\": \"Workvivo\",\n                \"type\": \"Company\"\n            }\n        ]\n    }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "{{baseURL}}/Users/:WorkvivoID",
                  "host": [
                    "{{baseURL}}"
                  ],
                  "path": [
                    "Users",
                    ":WorkvivoID"
                  ],
                  "variable": [
                    {
                      "key": "WorkvivoID",
                      "value": "123456"
                    }
                  ]
                },
                "description": "# Update User via SCIM\n\n## What This Endpoint Does\n\nThis endpoint updates an existing user in the system using the SCIM. The PUT operation replaces the entire user resource with the provided data.\n\n## SCIM Schemas\n\nThis request uses two SCIM schemas:\n\n- **`urn:ietf:params:scim:schemas:core:2.0:User`** - The core SCIM User schema containing standard user attributes\n    \n- **`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`** - The enterprise extension schema for additional organizational attributes\n    \n\n## Request Body Structure\n\n### Core User Attributes\n\n| Field | Type | Required | Description |\n| --- | --- | --- | --- |\n| `schemas` | Array | Yes | Array of SCIM schema URIs that define the structure of the user resource |\n| `externalId` | String | No | Unique identifier for the user in the external system |\n| `userName` | String | Yes | Unique identifier for the user, typically an email address |\n| `active` | Boolean | No | Whether the user account is active (true) or deactivated (false) |\n| `title` | String | No | The user's job title |\n\n### Name Object\n\nThe `name` object contains the user's name components:\n\n- `formatted` - The full name as it should be displayed\n    \n- `familyName` - Last name / surname\n    \n- `givenName` - First name / given name\n    \n\n### Emails Array\n\nArray of email addresses associated with the user. Each email object contains:\n\n- `value` - The email address\n    \n- `type` - The type of email (e.g., \"work\", \"home\")\n    \n- `primary` - Boolean indicating if this is the primary email\n    \n\n### Phone Numbers Array\n\nArray of phone numbers associated with the user. Each phone object contains:\n\n- `value` - The phone number\n    \n- `type` - The type of phone (e.g., \"work\", \"mobile\")\n    \n- `primary` - Boolean indicating if this is the primary phone number\n    \n\n### Addresses Array\n\nArray of physical addresses associated with the user. Each address object can contain:\n\n- `locality` - City or locality name\n    \n- `type` - The type of address (e.g., \"work\", \"home\")\n    \n\n## Enterprise Extension Fields\n\nThe enterprise extension (`urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`) provides additional organizational attributes:\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `department` | String | The department the user belongs to |\n| `hireDate` | String (ISO 8601) | The date the user was hired |\n| `dateOfBirth` | String (ISO 8601) | The user's date of birth |\n| `manager` | Object | Information about the user's manager |\n| `taxonomies` | Array | Organizational taxonomy classifications |\n\n### Manager Object\n\n- `value` - The unique identifier of the manager\n    \n- `displayName` - The display name of the manager\n    \n- `$ref` - Reference URL to the manager's resource\n    \n\n### Taxonomies Array\n\nArray of organizational classifications. Each taxonomy object contains:\n\n- `displayName` - The name of the taxonomy value\n    \n- `type` - The type of taxonomy (e.g., \"Division\", \"Company\", \"Department\")\n    \n\n## Configuration\n\n**Important:** This request uses the `{{baseURL}}` variable which must be configured in your environment. Set this variable to your SCIM API base URL (e.g., `https://api.workvivo.com/scim/v1`).\n\n## Notes\n\n- This is a PUT operation, which means it replaces the entire user resource. All fields should be provided to avoid unintentionally clearing data.\n    \n- The user ID should be appended to the URL path when making the actual request"
              },
              "response": []
            }
          ]
        }
      ],
      "description": "This Postman collection provides endpoints for managing users within Workvivo.  \nIt supports creating, updating, retrieving, and deactivating user accounts.\n\n## Supported Resources\n\n- Users (`/scim/v2/Users`)\n    \n\n## Authentication\n\nAll endpoints require a Bearer token.\n\n## SCIM User Attributes\n\n**Schema:** `urn:ietf:params:scim:schemas:core:2.0:User`\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `id` | string | Server-generated Workvivo unique identifier (read-only) |\n| `userName` | string | Email address - match email.value (Mandatory) |\n| `externalId` | string | Unique identifier provided per user that will anchor user information for provisioning (Mandatory) |\n| `emails.value` | string | Email address - match userName value (Mandatory) |\n| `active` | boolean | Indicates whether the user is enabled (true/false) |\n\n---\n\n### Name\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `name.givenName` | string | First (given) name (Mandatory) |\n| `name.familyName` | string | Last (family) name (Mandatory) |\n| `displayName` | string | Display name |\n\n---\n\n### Email\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `emails.value` | string | Email address (Mandatory) |\n| `userName` | string | Email address - match email.value (Mandatory) |\n\n---\n\n### Phone Numbers\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `phoneNumbers.value` | string | Phone number |\n| `phoneNumbers.type` | string | work, mobile |\n\n---\n\n### Job Title\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `title` | string | Users Job Title |\n\n---\n\n### Address\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `locality` | string | Location (Secondary Team) |\n\n---\n\n## Enterprise User Attributes\n\n**Schema:** `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`\n\n### Team Data\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `department` | string | Department name(Primary Team) |\n| `costCenter` | string | Cost center (Tertiary Team) |\n| `Addtional taxonomies` | string | Additional Team types |\n\n---\n\n### Manager Data\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `manager.value` | string | SCIM ID of the user's manager |\n\n---\n\n### Hire Date\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `hireDate` | dateTime | Users Hire Date - Format YYYY-MM-DD |\n\n---\n\n### Date of Birth\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `dateOfBirth` | dateTime | Users Date of Birth - Format YYYY-MM-DD |\n\n---\n\n### Custom Field\n\n| Attribute | Type | Description |\n| --- | --- | --- |\n| `CustomField` | string | Additional Custom Fields to the 'Other Information' |\n\n---\n\n## Filtering & Query Parameters\n\n| Parameter | Description |\n| --- | --- |\n| `filter` | SCIM filter expression (e.g., `userName eq \"jdoe\"`) |\n| `startIndex` | Pagination start index |\n| `count` | Number of results per page |\n| `sortBy` | Attribute to sort results by |\n| `sortOrder` | `asc` or `desc` |\n\n---",
      "event": [
        {
          "listen": "prerequest",
          "script": {
            "type": "text/javascript",
            "packages": {},
            "requests": {},
            "exec": [
              ""
            ]
          }
        },
        {
          "listen": "test",
          "script": {
            "type": "text/javascript",
            "packages": {},
            "requests": {},
            "exec": [
              ""
            ]
          }
        }
      ]
    }
  ],
  "auth": {
    "type": "bearer",
    "bearer": [
      {
        "key": "token",
        "value": "",
        "type": "string"
      }
    ]
  },
  "event": [
    {
      "listen": "prerequest",
      "script": {
        "type": "text/javascript",
        "packages": {},
        "requests": {},
        "exec": [
          ""
        ]
      }
    },
    {
      "listen": "test",
      "script": {
        "type": "text/javascript",
        "packages": {},
        "requests": {},
        "exec": [
          ""
        ]
      }
    }
  ],
  "variable": [
    {
      "key": "baseURL",
      "value": "https://WORKVIVO_URL/scim/v2/scim"
    }
  ]
}