Atrium API
Verify
The verify endpoint begins a verification process for a member. It gathers information about account and routing numbers. Partners may optionally choose to include transaction data in this request, potentially avoiding a separate aggregate member request.
The verification workflow is similar to standard aggregation: Start the verification, poll the connection status, answer MFA if necessary by using the list member MFA challenges endpoint and the resume from MFA endpoint, poll the status again, then read the member's account numbers.
For more information on this and other aggregation-type processes, please see our developer guide.
Errors
- If a verification is already running, a
202 Acceptedstatus will be returned. - If an institution does not support verification, a
400 Bad Requesterror will be returned. - If verification is not enabled, a
403 Forbiddenstatus will be returned. If you see403 Forbiddenbut the member'sinstitutionnevertheless shows that verification is enabled, please contact support by submitting a ticket. - If another aggregation-type process is already running — like standard aggregation or extended transaction history — a
409 Conflictwill be returned.
Request Body
| Field | Required | Type |
|---|---|---|
include_transactions When set to | Optional | Boolean |