An update request is a JSON object to create, update or delete a person.
Table of Contents |
---|
Deleting a person
The payload’s properties are:
action | Value: Delete | string, Mandatory | ||
cid | The company ID of the person. You need to specify this value. | int, Mandatory | ||
pid, login, email | Use any of these three properties to uniquely identify the person to delete. The system will select in this order of priority: pid, then login, then email.
Examples:
| int?, string?, string? Mandatory | ||
data | An optional free-text information. It will be returned with the results for your convenience. | string, Optional |
Example:
Code Block |
---|
{ "action": "Delete", "pid": 677, "cid": 537, "data": "just a test" } |
Creating a person
The payload’s properties are:
action | Value: Create | string, Mandatory | ||
cid | The company ID of the person. You need to specify this value. | int, Mandatory | ||
The mandatory email. | string, Mandatory | |||
login | An optional login. Only specify if you want this user to be able to login. Note that no password will be assigned at this stage. | string?, Optional | ||
fname | First name. | string, Mandatory | ||
lname | Last name. | string, Mandatory | ||
title | Optional title of person, such as “Dr.”, “Mrs.” etc. | string?, Optional | ||
role | Optional role of the person, such as “Manager”. | string?, Optional | ||
code | Optional name abbreviation. If not specified, the system automatically picks the initial letters of first and last name. “John Good” => “JG” | string?, Optional | ||
phone | Optional phone number. | string?, Optional | ||
phoneMobile | Optional mobile phone number. | string?, Optional | ||
comments | Optional internal comments. | string?, Optional | ||
timezone | Optional time zone. If not specified then the person inherits the time zone of the company to which he/she is attached (recommended). To enumerate available time zones see: settings/timezones/codes | string?, Optional | ||
cfs | Optional person-level custom fields. It contains a collection of custom fields. Example:
You can reference custom fields by their numeric ID (see id) or their title (see t). The example above shows both approaches.
| object?, Optional | ||
active | Optional boolean. If you want the person to be able to login, you should:
| bool?, Optional | ||
profile | Optional integer. Use to assign a specific user profile. If the new person has a login and is active, it is recommended to explicitly assign a user profile. If you do not do so then the system will automatically assign a user profile on your behalf. This will typically be the first profile in alphabetical order. See User profiles to enumerate available profiles. | integer?, Optional | ||
data | An optional free-text information. It will be returned with the results for your convenience. | string?, Optional |
Example:
Code Block |
---|
{ "action": "Delete", "pid": 677, "cid": 537, "data": "just a test" } |
Deleting a person
The JSON properties are:
action | Either one of:
| string, Mandatory |
cid | Company ID. This property is mandatory. You do indeed need to find out the company to which the person is attached or shall be attached. By the way, it is not possible to change the company ID of an existing person. Once a person is attached to a company, this attachment is forever! | int, Mandatory |
pid | The unique ID of the person. When deleting or updating a person you need to provide any of the 3 possible identifiers: Id, Login, Email. | int?, Optional |
login | The login assigned to the person. When deleting or updating a person you need to provide any of the 3 possible identifiers: Id, Login, Email. The login is not mandatory and a person without a login is perfectly valid in Wordbee Translator. | string, Optional |
The email. When creating a new person you must specify the email. | string, Optional |