Assessment Invite Technical Steps
1. Authentication
- Use this guide to generate an
access_token. - The token generated will go in
Authorizationheader for all API calls.
2. Assessment Invite API
Every assessment invitation sent to Talview, must follow the below payload structure. Request header definition| Method | POST |
|---|---|
| Host | https://api.talview.com |
| Route | /api/rest/external/assessment/invite |
| Content type | application/json |
| Attribute | Mandatory | Data Type | Description |
|---|---|---|---|
| candidate_email | yes | String | Candidate’s email address |
| candidate_first_name | no | String | Candidate’s first name |
| candidate_last_name | no | String | Candidate’s last name |
| candidate_reference_id | no | String | Candidate’s ID in the external system |
| workflow_step_id | yes | Number | Workflow_step_id in Talview System (maps to the exact step in the workflow where the candidate needs to be invited) |
| workflow_step_reference_id | no | String | Workflow Step ID in the external system (Note: Either workflow_step_id or step_reference_id is manadatory) |
| callback_url | no | String | URL of the external service to be used for sending the reports, scores, playback video, etc. |
| is_notify | no | Boolean | Whether the candidate needs to be notified or not |
| valid_till | no | TimeStampz | Assessment window duration in ISO 8601 format: yyyy-MM-dd’T’HH:mm:ss.SSSZ |
-
Success response: HTTP status code - 201
-
Error response: HTTP status code - 422
-
Error response: HTTP status code - 400

