When to use
| Scenario | Example |
|---|---|
| Missing employer | User disclosed an additional employer after initial verification |
| Seasonal employment | User has a second job that wasn’t initially included |
Add an employer [Server-side]
Send aPOST request to the order’s /employers/ endpoint with the employer details.
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
company_name | string | No | Employer name |
company_domain | string | No | Company website domain |
start_date | date | No | Job start date (YYYY-MM-DD) |
end_date | date | No | Job end date (YYYY-MM-DD) |
suborder_number | string | No | Your external ID for tracking |
company_address | object | No | Employer address with street, city, state, zip |
The order must be in an active state, not expired or canceled. Check the order status before adding employers.
What happens next
After adding the employer, Truv extends the order to include the new employer. The user receives a notification to connect their additional employer through the hosted verification page. Listen fortask-status-updated webhooks to know when the new employer’s data is ready.
Next steps
Data Refresh
Pull updated data without user re-authentication
New User
Create a hosted order from scratch
Deeplinking
Pre-fill employer info to skip search