Note |
---|
Make sure you set the HTTP Content-Type header to be application/json. |
Section | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
Making API Requests
|
Request Object Attributes
Attribute | Type | Limits | Possible Names | Description |
---|---|---|---|---|
apiToken | String | 50-character alphanumeric including dashes. | apiToken | (Required)Your supplied API Token. |
unique_id | String | 50-character alphanumeric including dashes. | (Required)Your unique_id. | |
login_source | String | 20-character alphanumeric including dashes. | (Required)Your supplied login source. | |
first_name | String | 50-character alphanumeric including dashes. | (Optional) User's first name | |
last_name | String | 50-character alphanumeric including dashes. | (Optional) User's last name | |
user_name | String | 50-character alphanumeric including dashes. | (Optional) Unique username | |
String | 100-character alphanumeric including dashes. | (Optional) Valid email address | ||
street | String | (Optional) User's first address | ||
city | String | 50-character alphanumeric including dashes. | (Optional) User's first address | |
province | String | 2-character postal abbreviation eg. "MA" | province, state | (Optional) User's first address |
postal_code | String | 20-character alphanumeric including dashes. | postal_code, zip | (Optional) User's first address |
street2 | String | 20-character alphanumeric including dashes. | (Optional) User's second address | |
city2 | String | 50-character alphanumeric including dashes. | (Optional) User's second address | |
province2 | String | 2-character postal abbreviation eg. "MA" | province2, state2 | (Optional) User's second address |
postal_code2 | String | 20-character alphanumeric including dashes. | postal_code2, zip2 | (Optional) User's second address |
phone_cell | String | 20-character alphanumeric including dashes. | (Optional) | |
user_type_id | String | Id number of UserType | (Optional) | |
employ_no | String | 50-character alphanumeric including dashes. | (Optional) | |
employee_phone | String | 50-character alphanumeric including dashes. | (Optional) | |
student_no | String | 50-character alphanumeric including dashes. | (Optional) | |
student_phone | String | 50-character alphanumeric including dashes. | (Optional) | |
driver_licence_num | String | 255-character alphanumeric including dashes. | driver_licence_num, driver_license_num | (Optional) |
date_of_birth | String | 10-character date in format 'yyyy-mm-dd' | (Optional) | |
locker_user_type_id | String | Id number of LockerUserType | (Optional) | |
driver_licence_prov | String | 2-character postal abbreviation eg. "MA" | driver_licence_prov, driver_license_state | (Optional) |
Successful Response
The response will be a json object.
Content-Type: application/json
Code Block | ||||
---|---|---|---|---|
| ||||
{ "status": "success", "reference_id": 44 } |
Related Pages
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|
Show if | ||
---|---|---|
| ||
In order for a client to use this, they would have to have paid for the right to integrate with OPS-COM, been issued an API Key and had their integration validated by testing with us. Server setup nGinx needs to have Access-Control-Allow-Origin : * to work. The controller also needs to be behind a certificate. Client Setup There is some setup related to getting clients to use the API. First, they must have an API token that exists on the API token table. They then have to have an api_permission record that lists what kind of permission the token can have. The permission needed for this api request is user-create. |