Skip to main content
Add a new employer to an existing order when additional employment connections are needed after the order was originally created. The order must not be expired or canceled.

​
When to use

ScenarioExample
Missing employerUser disclosed an additional employer after initial verification
Seasonal employmentUser has a second job that wasn’t initially included

​
Add an employer [Server-side]

Send a POST request to the order’s /employers/ endpoint with the employer details. 
curl --request POST \
     --url https://prod.truv.com/v1/orders/39aa1486ccca4bc19cda071ffc1ba392/employers/ \
     --header 'X-Access-Client-Id: YOUR_TRUV_CLIENT_ID' \
     --header 'X-Access-Secret: YOUR_TRUV_CLIENT_SECRET' \
     --header 'Content-Type: application/json' \
     --data '{
  "company_name": "Facebook Demo",
  "company_domain": "facebook.com",
  "start_date": "2019-08-24",
  "company_address": {
    "street": "1 Hacker Way",
    "city": "Menlo Park",
    "state": "CA",
    "zip": "94025"
  }
}'

​
Request fields

FieldTypeRequiredDescription
company_namestringNoEmployer name
company_domainstringNoCompany website domain
start_datedateNoJob start date (YYYY-MM-DD)
end_datedateNoJob end date (YYYY-MM-DD)
suborder_numberstringNoYour external ID for tracking
company_addressobjectNoEmployer 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 (if configured) to connect their additional employer through Bridge. Listen for task-status-updated webhooks to know when the new employer’s data is ready.

​
Next steps

Data Refresh

Pull updated data without user re-authentication

Follow-up

Re-engage users who didn’t finish verification

Self-Certification

Let users review and confirm retrieved data