The endpoints are https://yourhubsolv.hubsolv.com/api/client/format/json/ or https://yourhubsolv.hubsolv.com/api/client/format/xml/
The API requires you send a username and password using HTTP Basic Authentication when posting or making requests as an additional layer of security. You can find your username and password by navigating to Settings > API Settings in your Advize. This is transmitted in the header envelope of your request in the format Authorization: Basic yourusername:yourpassword where the username and password separated by a colon are base64 encoded.
An incorrect username and password will return a status of false along with an error message:
JSON:
{"status":false,"error":"Not authorized"}
XML:
<xml><status>0</status><error>Not authorized</error></xml>
The Advize API accepts input as Key Value pairs.
You are required to post your Advize API key as a means of authentication.
This can be found by navigating to Settings > API Settings in your Advize.
HUBSOLV-API-KEY=1718debe6fcde8124494c1116bb26fbe45755d1
An incorrect API key will return a status of false along with an error message:
JSON:
{"status":false,"error":"Invalid API Key."}
XML:
<xml><status>0</status><error>Invalid API Key.</error></xml>
Successful post to the API will return a status of "success_post" along with the id of the client record that has been created:
JSON:
{"status":"success_post","id":26}
XML:
<xml><status>success_post</status><id>26</id></xml>
We do not accept JSON in the body of the request, all requests must be normal form posts, key value pairs.
These are fields which you can post into via the API in to the Client Details module
If obtaining partner information, fields should be updated to add partner_ to the beginning. If the field includes client_ this should be replaced with partner_
Field |
Field Name |
Field Restriction |
Notes |
|---|---|---|---|
Title |
|
|
enum |
First, names(s) |
|
|
string |
Middle name |
|
|
string |
Last name |
|
|
string |
Other/Previous Names |
|
|
string |
Security Question |
|
|
string |
Answer |
|
|
string |
Place Of Birth |
|
|
string |
Date Of Birth |
|
|
string |
Marital status |
|
|
enum |
Marital Status Since |
|
|
string |
Gender |
|
|
enum |
Home phone no |
|
|
string |
Home phone no: Out of Service |
|
|
integer |
Mobile no |
|
|
string |
Mobile no: Out of Service |
|
|
integer |
Work phone number |
|
|
string |
Work phone number: Out of Service |
|
|
integer |
Best time to call |
|
|
enum |
Preferred contact method |
|
|
enum |
|
|
string |
|
Service - Permission to contact by; Home Phone |
|
|
integer |
Service - Permission to contact by: Mobile Phone (Call) |
|
|
integer |
Service - Permission to contact by: Work Phone |
|
|
integer |
Service - Permission to contact by: Email |
|
|
integer |
Service - Permission to contact by: SMS |
|
|
integer |
Service - Permission to contact by: Mail |
|
|
integer |
Marketing - Permission to contact by; Home Phone |
|
|
integer |
Marketing - Permission to contact by: Mobile Phone (Call) |
|
|
integer |
Marketing - Permission to contact by: Work Phone |
|
|
integer |
Marketing - Permission to contact by: Email |
|
|
integer |
Marketing - Permission to contact by: SMS |
|
|
integer |
Marketing - Permission to contact by: Mail |
|
|
integer |
Employment status |
|
|
enum |
Occupation |
|
|
string |
Address line 1 |
|
|
string |
Address line 2 |
|
|
string |
Address line 3 |
|
|
string |
Town |
|
|
string |
County |
|
|
string |
Post Code |
|
|
string |
Country |
|
|
string |
Time at address? Years |
|
Whole Number
|
integer |
Time at address? Months |
|
Whole Number
|
integer |
No longer at this address |
|
|
integer |
Consent Given to Discuss with a 3rd Party (Relative / Health Worker / Doctor) |
|
|
integer |
3rd Party: Title |
|
|
enum |
3rd Party: First name(s) |
|
|
string |
3rd Party: Last name |
|
|
string |
3rd Party: Relationship |
|
|
string |
3rd Party: Phone No |
|
|
string |
3rd Party Phone No: Out of Service |
|
|
integer |
3rd Party: Best time to call |
|
|
enum |
3rd Party: Email Address |
|
|
string |
3rd Party: Address line 1 |
|
|
string |
3rd Party: Address line 2 |
|
|
string |
3rd Party: Address line 3 |
|
|
string |
3rd Party: Town |
|
|
string |
3rd Party: County |
|
|
string |
3rd Party: Post Code |
|
|
string |
3rd Party: Country |
|
|
string |
3rd Party: Notes |
|
|
string |
Vulnerability Level |
|
|
enum |
Type(s) of Vulnerability |
|
|
comma separate for multiple |
Vulnerability Details |
|
|
string |
Print Letters in Large Font? |
|
|
integer |
Authority to Share Info with 3rd Parties |
|
|
integer |
Authority to Store Information |
|
|
integer |
Review Required |
|
|
integer |
Review Date |
|
|
string |
Client Deceased |
|
|
integer |
Date Informed |
|
|
string |
Informed by |
|
|
enum |
3rd Party: Title |
|
|
enum |
3rd Party: First name(s) |
|
|
string |
3rd Party: Last name |
|
|
string |
3rd Party: Relationship |
|
|
enum |
3rd Party: Phone No |
|
|
string |
3rd Party: Best time to call |
|
|
enum |
3rd Party: Email Address |
|
|
string |
3rd Party: Address line 1 |
|
|
string |
3rd Party: Address line 2 |
|
|
string |
3rd Party: Address line 3 |
|
|
string |
3rd Party: Town |
|
|
string |
3rd Party: County |
|
|
string |
3rd Party: Post Code |
|
|
string |
3rd Party: Country |
|
|
string |
3rd Party: Notes |
|
|
string |
Evidence received |
|
|
integer |
Take Partner's details? |
|
|
integer |
Same address? |
|
|
integer |
Comments
0 comments
Please sign in to leave a comment.