- your
osa_test_key, sent by OSA through a one-time link; - the sign-in for one of your test accounts, and the OSA app from the App Store. OSA sends your firm the test accounts and their passwords; if you don’t have one, ask whoever at your firm received them.
1
Check your key
"environment": "test", and the key’s scopes (its permissions).2
Find your test accounts
osa_id of one with "status": "active".3
Send a claim
201 Created with OSA’s claim id, your external_id, "test": true, and "assignment": { "status": "pending_acceptance", … }.If the call times out, send exactly the same request again with the same Idempotency-Key: run the curl again without the first line. You get 201 with the claim’s current state, and no second claim is created.4
Accept it in the app
Sign in to the OSA app as the test account. The claim is in Incoming, marked TEST. Tap Accept.
5
See the acceptance
assignment now shows "status": "accepted" and a responded_at time. In production you would run this poll every few minutes; see Polling.Next steps
- Try a rejection: reject a test claim in the app, read the
rejection_reason, then offer it to another test account withPOST /v1/claims/{id}/assignment. - Send more of what your claims system knows: see Claim details, Occupancy and building type and Carrier details.
- Handle every error your code can receive: see Errors.
- Read Testing with test accounts before you plan your go-live.