Get an ACH Pull
New in v3: v2 has no equivalent.
Authorization:
Every request is signed with your API key: a short-lived JWT, signed with your private key, sent in one header on /v3/* and /api/v2/* alike.
Headers:
Authorization: APIKey {SIGNED_JWT}
How to build and sign the JWT: Authentication.
Endpoint
/v3/banking/ach-pulls/{ach_pull_id}
Path parameters
| Parameter | Type | Description |
|---|---|---|
ach_pull_id | string (ach_…) | Required. The pull. |
An account-scoped key reads only its own account's pulls; another account's reads as 404. A workspace-scoped key reads any pull of the workspace.
Response Schema
The pull, with the fields of a Request an ACH Pull response. A completed pull answers what of it is held in the reserve (reserved) and what became spendable (available); source is the account it debited.
{
"id": "ach_01m5b9m806f9vvh40n5ykctvz4",
"account_id": "cst_01m4tvfffve0k9ak5mbn9pf6vn",
"pull_account_id": "bpa_01m5b6jwn6fq28h3rx6m937c67",
"bank_account_id": "bnk_01m4tw439jffgvhtmkh73gk596",
"amount": { "amount": "250.00", "currency": "USD" },
"fee": { "amount": "0.00", "currency": "USD" },
"total": { "amount": "250.00", "currency": "USD" },
"reserved": { "amount": "25.00", "currency": "USD" },
"available": { "amount": "225.00", "currency": "USD" },
"source": {
"name": "Operating at Chase", "bank_name": "JPMorgan Chase",
"holder_name": "Acme Corp", "holder_type": "business",
"routing_number": "021000021", "account_number_last4": "4321", "account_type": "checking"
},
"status": "completed",
"status_reason": "Hold over, credit available",
"sec_code": "CCD",
"description": "Top up",
"grace_ends_at": "2026-10-19T23:59:23Z",
"posted_at": "2026-10-20T00:01:25Z",
"available_at": "2026-10-23T00:01:25Z",
"completed_at": "2026-10-23T00:01:30Z",
"created_at": "2026-10-19T23:58:23Z",
"updated_at": "2026-10-23T00:01:30Z"
}
In the account's transactions (v2 List Transactions) the pull is a bank deposit on the ach rail whose bankTransactionDetails.achPullId is the pull's id.
Errors
| Status | message | When |
|---|---|---|
400 | failed to parse request | ach_pull_id is not an ach_… id. |
401 | unauthorized | Missing or invalid signature. |
404 | ach_pull_not_found | No such pull, or it belongs to another account. |
Support and Resources
If you need assistance or have any questions, our support team is here to help. You can contact our support team at support@blockwyre.com.
Stay Updated
Stay up-to-date with the latest news, updates, and features from BlockWyre by following us on social media:
- Instagram: BlockWyre Instagram
- Twitter: BlockWyre Twitter
- Facebook: BlockWyre Facebook
- LinkedIn: BlockWyre LinkedIn
We are excited to have you on board and look forward to seeing how you leverage BlockWyre's powerful tools to enhance your financial operations. Happy integrating!