Delete a Bank Counterparty
Retires a US withdrawal destination. It is no longer listed, and a new withdrawal cannot name it. The record is kept, so a withdrawal already sent still finds it. Saving the same reference again creates a new counterparty; the deleted one's id does not come back.
There is no refusal while a withdrawal to it is open, and there is no webhook.
An account-scoped key deletes only its own account's counterparties; another account's reads as 404. A workspace-scoped key deletes any US counterparty of the workspace.
Replaces DELETE /api/v2/banking/counterparties/{id}.
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/counterparties/{counterparty_id}
Path parameters
| Parameter | Type | Description |
|---|---|---|
counterparty_id | string (bcp_…) | Required. The counterparty. |
Response
204 No Content.
Errors
| Status | message | When |
|---|---|---|
400 | failed to parse request | counterparty_id is not a bcp_… id. |
401 | unauthorized | Missing or invalid signature. |
404 | bank_counterparty_not_found | No such counterparty, it was already deleted, it belongs to another account, or the id is not a US counterparty. |
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!