Village Product and Developer Docs
  • 📘Welcome to Village Labs
    • Welcome to Village Labs
    • Self Service Onboarding
    • Help Pages
      • Adding and Deleting Users
      • Mapping Users to Source tool IDs
      • How to follow or unfollow other users
      • Configuring & Removing Daily Slack Notification Whitelist
      • Changing the Reporting Lines & Teams
      • Following Custom Reports
      • Google Drive Privacy: When will my documents appear in Village Reports?
    • Custom Reports
      • Creating Team Reports
      • Creating Custom Reports & Custom Prompt Library
    • Meetings
      • Connecting your Calendar
      • Configuring your Meetings
      • Meeting Summary Reports
    • Village Assistant
      • Github PR Review Tool
    • Security & Compliance
    • Data Privacy & Permissions
  • 🔌Data Connections
    • Airtable
    • Ashby
    • Clickup
      • Finding ClickUp User IDs
    • Figma
    • Github
      • Finding GitHub User IDs
    • Gitlab
    • Google - OAuth (Recommended)
    • Google - Manual Connection
    • Hubspot
    • Jira
      • Finding Jira User IDs
    • Confluence
      • Finding Confluence / Jira User IDs
    • Linear
    • Asana
    • Monday
    • Notion
    • Pipedrive
    • Slack
    • Basecamp
    • Zoom
  • 👩‍💻Legacy Developer Docs
    • Developer Quickstart
    • Village APIs: Introduction
      • Activity API
      • User Status API
      • Patch User API
      • Segments API
      • Redemption API
      • Master Award Controls
      • Connections (Referrals) APIs
      • GET APIs
    • 3rd Party Payments Integrations
    • Embedding Village Dashboards
  • 🕵️LEGACY Knowledge Base
    • Admin Quickstart
    • Referrals Support
    • The Basics of Village in 15 Minutes
    • Programs & Rules
      • Triggers
        • Activities
        • Goals
      • Conditions
        • Segment Conditions
        • Time Conditions
        • Max Budget Conditions
        • Conditional Multipliers
    • Awards
      • Monetary (Cash) Awards
      • Non-Monetary Awards
        • Funding
          • In-depth use cases for funding pools
      • Badges & Statuses
      • Award Expiration
    • Segments
      • Segmentation Use Cases
    • Rule Evaluation Logic Deep-dive
    • The Village Dashboards
      • Admin Account Creation
      • User Access Management
      • Network Settings
      • User Dashboard
    • BigQuery
    • Managing Payment Integrations
    • Referrals (Connections)
      • Pre-populating Users' Unique Referral Codes In Signup Flows & Forms
  • No and Low Code Solutions
    • No and Low Code Solutions
      • No & Low Code Solutions
  • Feedback
    • Village Docs Feedback Form
    • Feature Requests
    • Talk to our Team
Powered by GitBook
On this page
  • Endpoint Path
  • Headers
  • Request Example
  • Body Fields
  • Use Cases

Was this helpful?

  1. Legacy Developer Docs
  2. Village APIs: Introduction

Patch User API

Make a PATCH request to update user information for existing users in Village.

PreviousUser Status APINextSegments API

Last updated 1 year ago

Was this helpful?

For detailed use cases and more advanced features, visit the to explore the endpoints and possible implementations.

When to use Patch User vs User Status?

  1. User Status API is primarily for creating users, and allows you to add key user information when creating them

  2. The Patch User API to update personal and contact information of existing users

  3. NOTE: Editing other user data requires the use of case-specific APIs, such as or

Make a PATCH request to the Patch User API update basic user information for existing users in the Village System. Examples of data that can be updated are first name, last name, and contact phone number. It is a secure and efficient way to keep user information up-to-date.

Endpoint Path

PATCH https://app.villagelabs.net/networks/{network_id}/users/{user_email}

Replace {network_id} with your actual Network ID and {user_email} with the email of the user you want to update. These can be found in the Admin Dashboard.

Headers

As with all other Village API endpoints, the usual headers are required authenticate the PATCH request. See details in .

Header
Value

Content-Type

application/json

Accept

application/json

Authorization

Bearer API_KEY

Request Example

To update a user's information, make a PATCH request to the endpoint with a JSON body containing the new data.

JSON Body:

{
    "first_name": "NewFirstName",
    "last_name": "NewLastName",
    "phone_number": "+15555555555"
}

Replace NewFirstName and NewLastName with the updated first and last names of the user, and +1 555 555 5555 with the user's new contact phone number.

Body Fields

  • first_name - The new first name of the user.

  • last_name - The new last name of the user.

  • phone_number - The new contact phone number for the user, in international format.

Use Cases

This API is particularly useful when you need to:

  • Backfill existing users' name or contact information

  • Correct user information

  • Update user details following a name change

  • Change the contact phone number if the previous one is no longer in use.

👩‍💻
Village Postman collection
editing referral connections
changing segment memberships
API Introduction