Atrium API
Identify
The identify endpoint begins an AOI process for an already-existing member. It gathers information about account owners. Partners may optionally choose to include transaction data in this request, potentially avoiding a separate aggregate member request.
The identification workflow is similar to standard aggregation: Start the identification, 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, please see our Atrium developer guide.
Errors
- If an identification job is already running, a
202 Acceptedstatus will be returned. - If an institution does not support identification, a
400 Bad Requesterror will be returned. - If identification is not enabled, a
403 Forbiddenstatus will be returned. If you see403 Forbiddenbut the member'sinstitutionnevertheless shows that identification 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.
POST
/users/{user_guid}/members/{member_guid}/identify
Request Body
| Field | Required | Type |
|---|---|---|
include_transactions When set to | Optional | Boolean |
Request sample
Language:sh
Response sample
Language:json