Ensure the person record already has first_name, last_name, dob, email or phone_number, legal_address, and ssn (or another personal_ids identifier) set before calling the verification endpoint.
POST to https://api.synctera.com/v0/verifications with a JSON body containing: result (e.g., ACCEPTED), verification_time (ISO 8601), verification_type (IDENTITY), person_id, and a vendor_info object identifying the external provider.
Optionally include a details array with individual check results — each entry may carry a category, result (PASS/FAIL), score, and vendor_code.
Inspect the 201 response to obtain the verification id and confirm the result field reflects the submitted determination.
If the partner's risk team requires review, expect a REVIEW result and watch for any follow-up requests for additional document verification via POST /v0/verifications with verification_type DOCUMENT_VERIFICATION.
Use GET /v0/verifications/{id} to poll the status or subscribe to CUSTOMER.* webhook events for automated updates.
Known gotchas
The correct endpoint is POST /v0/verifications (not /v0/verifications/verify nor /v0/kyc/verifications) — confirmed in the API reference at docs.synctera.com/reference/createverification.
Exactly one of person_id or business_id must be present in the request body; supplying both or neither returns a 400.
The deprecated KYC Verification section still appears in the Synctera sidebar — always use the KYC/KYB Verifications group endpoints instead.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp