Edit
Updates an existing consultant.
When updating you have to specify the "id" parameter to either the consultant email or the id-number from Brainville.
If using email to identify a consultant, the email address must be unique for the consultants at your company in Brainville.
End point
/consultantapi/edit
Request format
POST
| Property Name |
Required |
Description |
id |
No |
Used to identify the resource to update.
This can either be the unique email address of the resource, or the numeric id-number found in Brainville for the resource.
If email is used, and the email is found not to be unique, the resource will not be updated and the error code "DuplicateEntity" will be returned |
firstname |
Yes |
|
lastname |
Yes |
|
email |
Yes |
|
active |
No |
If the resource should be active (visible in lists).
Possible values: true or false
Defaults to true |
mobile |
No |
Mobile phone number |
linkedin |
No |
URL to LinkedIn page |
twitter |
No |
URL to twitter page |
role |
No |
The primary working role of the resource, for example "Project Manager" or "Java Developer" |
description |
No |
Descriptive text used to promote the resource |
picture |
No |
PNG-picture of the resource, converted to a Base64 string |
experiences |
No |
List of experience elements |
educations |
No |
List of education elements |
skills |
No |
List of skills |
roles |
No |
List of roles |
languages |
No |
List of spoken languages
Format:
<languages>
<language></language>
</languages> |
preferences |
No |
See Preference element |
strengths |
No |
List of character/work related strengths
Format:
<strengths>
<strength></strength>
</strengths> |
personalitytraits |
No |
Consultant personality traits, as a list of qna elements |
personalitytests |
No |
List of personalitytest element |
worksamples |
No |
List of worksample elements |