User API
- 1 User Object
- 2 GET /users V3
- 3 GET /users/:id V3
- 4 POST /users/sso V3
- 4.1 GET parameters
- 4.2 POST Parameters
- 4.3 POST Parameters required in order to be able to e-prescribe for this user
- 4.4 Response
- 4.4.1 Guest SSO
- 4.4.2 Patient SSO
- 4.4.2.1 Provider SSO
- 5 GET /auth V3
- 6 POST /users/login.json [public access] V3
- 7 GET /me V3
- 8 POST /me V3
- 8.1 Timezone List
- 9 POST /users/logout V3
- 10 POST /tokens/refresh V3
- 11 POST /users/reset_password V3
- 12 POST /users/alive V3
- 13 POST /users/activate V3
User Object
Type
Value | Meaning | Description |
---|---|---|
|
| Admin user |
|
| For system use |
|
| For system use |
|
| Admin user |
|
| For system use |
|
| A registered patient |
|
| Â |
|
| Provider: Physician or CSR |
|
| Guest one-time user |
|
| User joined by dial-in |
|
| deprecated |
Subtype
Value | Meaning | Description |
---|---|---|
|
| Remote Medic |
|
| Licensed Service Provider |
|
| Remote Medic |
|
| deprecated |
|
| Customer Service Representative |
|
| Medical Assistant |
Â
GET /users V3
Filter Parameters
Parameter | Type | Description |
---|---|---|
|
| E.g:
|
|
| Full text search (minimum 3 chars) |
String | Like search (minimum 3 chars) | |
|
| Search keyword (minimum 3 chars)
Should be used in conjunction with |
|
|
|
|
| |
|
| Â |
|
| Status, e.g:
|
|
| User type, e.g:
|
|
| Role, e.g:
|
| Â | Â |
| Â | Â |
| Â | Clinic group |
| Â | Provider sub type |
Other Parameters
Parameter | Type | Description |
---|---|---|
|
| E.g:
|
|
| Offset |
|
| Page size |
|
| E.g:
Available fields params
|
Â
Response:
curl --location 'https://api-vclinic.vseepreview.com/vc/stable/api_v3/users?q=anton%2Bpatient1%40vseelab.com&type=200' \
--header 'X-ApiToken: vclinic_api_token' \
--header 'X-AccountCode: vclinic'
{
"data": [
{
"email": "anton+patient1@vseelab.com",
"id": "20008869839",
"full_name": "Anton Patient1"
},
...
],
"total_count": 500
}
Â
GET /users/:id V3
Get profile’s data of a particular user, including fields from the extended profile (if any).
Response:
curl --location --request GET 'https://api-vclinic.vsee.me/api_v3/users/27769243' \
--header 'X-ApiToken: xxxxxxxxxxxxx' \
--header 'X-AccountCode: vclinic'
{
"data": {
"id": "27769243",
"code": "63f67706de344db98a6461d00adc646e",
"first_name": "anton",
"last_name": "test_2",
"full_name": "anton test_2",
"username": "anton+test2@vseelab.com",
"vseeid": "cmo+user27769243",
"dob": "1980-01-01",
"email": "anton+test2@vseelab.com",
"gender": 1,
"active": true,
"tos": true,
"status": 20,
"subtype": "",
"timezone": "Europe/Berlin",
"email_verified": true,
"signup_step": 99,
"extra": {
"marital_status": "married",
"gender_identity": "Choose Not To Disclose",
"social_security_no": "",
"veteran": "",
"race": "",
"ethnicity": "",
"health_insurance": "",
"insurance": "",
"insurance_policy_number": "",
"attachments": null,
"emerg_contact_name": ""
},
"dashboard_url_alternative": "/u/uat",
"account_code": "vclinic",
"clinics": [
"vclinic"
],
"rooms": [
{
"id": "865244556",
"code": "vclinic_room_code",
"slug": "uat",
"name": "UAT",
"account_code": "vclinic",
"domain": "vclinic.vsee.me",
"default": true,
"added_time": 1677096710,
"source": "signup"
}
],
"created": 1677096710,
"type": 200
}
}
POST /users/sso V3
Single Sign On for patient and provider.
This is disabled by default, you need to contact admin@vsee.com to request for it.
SSO process will create a user record on VSee side when you first call this API and will map to and return existing user record for further requests.
GET parameters
Use POST /users/sso?fields=vsee parameter to include the following object as part of the response. This may be used for Browser Call SDK workflow.
"vsee": {
"id": "ccpreview+606ce3e353c8411a8e7b52c664457b1f",
"token": "78fc497ff743d2b51050d9102acabe63"
}
POST Parameters
Parameter | Type | Description |
---|---|---|
|
|
|
|
|
|
|
|
YYYY-MM-DD format |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
POST Parameters required in order to be able to e-prescribe for this user
Parameter | Type | Description |
---|---|---|
|
|
|
|
|
|
|
|
YYYY-MM-DD format |
|
|
|
|
|
Max length: 128 character |
|
|
male / female |
|
|
|
|
|
|
|
|
Two-Letter State Abbreviation |
|
|
|
|
|
|
Response
Note: you can use the data.token.token return here to redirect user from your portal to VSee Clinic portal, please see Workflows section.
Guest SSO
Patient SSO
Provider SSO
GET /auth V3
Use this URL when you need to provide the user with a button or link to redirect to VSee Clinic. The URL will follow this pattern
https://vclinic.vseepreview.com/auth?sso_token={token}&next={next_url}
e.g
https://vclinic.vseepreview.com/vc/next/auth?sso_token=66bcd0acff324e8a44992d9596b5d361&next=/u/clinic
This will log user in, then redirect user to
https://vclinic.vseepreview.com/vc/next/u/clinic
Parameters
Parameter | Type | Description |
---|---|---|
|
| SSO token from User API - SSO API response |
|
| URL path to redirect the user to after login |
|
| 1 - invalidate the sso_token after login. This is optional for additional security. |
|
| 1 - disable all email communication |
POST /users/login.json [public access] V3
Log user in and retrieve access token
Notes:
user_type will be member(200), provider(400), …, etc
There is 2 methods for log in
active user
use username and password field
inactive user
user email and email token sent to their email
only after user update their password via API, their status will change to active and can log in via active user log in method above.
Parameters
Parameter | Type | Description |
---|---|---|
|
| (for active user only) |
|
| (for active user only) |
|
| (for non-active user who has not set the password yet) |
|
| (for non-active user who has not set the password yet) |
Response
Note: you can use the token.token return here to redirect user from your portal to VSee Clinic portal, please see Section Web log in using SSO Token.
GET /me V3
Retrieve the current user profile
Parameters
Parameter | Type | Description |
---|---|---|
|
|
|
Response
POST /me V3
Update current user profile
Parameters
Parameter | Type | Description |
---|---|---|
|
| (optional) Should be sent alone if it’s first time setting password, or together with old_password to change it. |
|
| (optional) Should be sent when user is changing password |
|
| (optional) yyyy-mm-dd |
|
| (optional) male / female |
|
| (optional) choose 1 from the list e.g Vietnamese |
|
| 0 - not accepting / 1 - accepted Terms of service |
|
| (optional) phone number |
|
| (optional) First name |
|
| (optional) Last name |
|
| (optional) Street addr |
|
| (optional) 2 letter state code (CA, AL) |
|
| (optional) eg 07123 |
|
| (optional) City |
|
| (optional) Primary Care Physician Name |
|
| (optional) Primary Care Physician Phone (10 digit) |
|
| (optional) See timezone list below |
|
| (optional) File id retrieved from |
To delete the uploaded avatar, pass empty string. lat
, long
??? gps | Object | json object, min lat, long
Timezone List
Response
POST /users/logout V3
Log the current user session out corresponding to the supplied tokens. The supplied tokens will be destroyed.
Parameters
Parameter | Type | Description |
---|---|---|
|
| Array of tokens to be destroyed, e.g |
Response
POST /tokens/refresh V3
Use refresh token to generate a new access token. New refresh token is also returned for the next refresh.
Parameters
Parameter | Type | Description |
---|---|---|
|
| Â |
Response
POST /users/reset_password V3
System will send reset password email to the email supplied if valid
Parameters
Parameter | Type | Description |
---|---|---|
|
| Valid email to send reset password email |
Response
POST /users/alive V3
When user is in critical workflow such as waiting for provider to call, it's required to send keep alive at certain interval recommended < 1/2 of the heartbeat value. Only "alive" patients will be able to show up on provider dashboard
Parameters
Parameter | Type | Description |
---|---|---|
|
| (optional) default value is 300s, you can set your own heartbeat value, the more intermittent your network connection, the higher the value you should set. Ideally for mobile, set to about 300s and update every 250s |
Response
POST /users/activate V3
It will check user info against eligibility file if configured for the current account. User will receive email with activation code.
Parameters
Parameter | Type | Description |
---|---|---|
|
| Â |
|
| Â |
|
| e.g |
|
|
|
|
| 4 digits e.g |
Response
Â