Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Definition
https://www.yammer.com/api/v1/users.json
Parameters
Name | In | Required | Type | Description |
---|---|---|---|---|
body | string | Email for new user | ||
full_name | body | string | Full name of user | |
job_title | body | string | Job title for the new user | |
department_name | body | string | Department name for the new user | |
location | body | string | Location for the new user | |
mobile_telephone | body | string | Mobile telephone number for the new user | |
summary | body | string | Summary for the new user. Typically used for a bio or description. |
Documentation
he users endpoint can be used to create new users in a Yammer network. It is strongly recommended that users are added through Microsoft 365 Admin Portal, Azure AD PowerShell, Azure AD Portal, Bulk Update, etc. instead of through this endpoint.
The behavior of this endpoint is dependent on factors, including:
- Whether the network is in Native Mode), or not.
- If the network is enterprise or freemium (basic.)
- Whether the user is a verified admin, or not.
- If the token passed to this endpoint is associated with a canonical (home) network, or an external network.
- Type of email passed to this endpoint (work versus personal.)
- Data residency of the Yammer network.
Over time all Yammer networks will transition to Native Mode and all user creation and updates will occur via Azure Active Directory.
Additional legacy parameters
Name | Type |
---|---|
im_provider | |
im_username | |
work_telephone | |
work_extension | |
external_profiles | |
significant_other | |
kids_names | |
interests | |
expertise | |
education | accepts multiple attributes i.e. education[]=UCLA,BS,Economics,1998,2002&education[]=USC,MBA,Finance,2002,2004 |
previous_companies | accepts multiple attributes i.e. previous_companies[]=Geni.com,Engineer,2005,2008 |