Stop allowing a member to pay you
Takes effect on the next settlement. Nothing already settled is affected: the list is policy for what may be paid, never a record of what was.
Takes effect on the next settlement. Nothing already settled is affected: the list is policy for what may be paid, never a record of what was.
Authorization
bearer In: header
Path Parameters
The connected member id.
Header Parameters
Act on behalf of one of your sub-clients. The value is that sub-client id, and the request then reads and writes that sub-client's own accounts and registry rows rather than yours. Omit it to act as yourself. A route that does not accept the header refuses it with 400 ON_BEHALF_OF_NOT_ALLOWED_HERE rather than ignoring it — that includes every vault route (deposits, withdrawals, conversions, sub-accounts, positions), the webhook registry, and POST /sub-clients, since a sub-client never has sub-clients of its own. An id that is not one of your sub-clients answers 404 ON_BEHALF_OF_NOT_FOUND; a closed one answers 409 ON_BEHALF_OF_SUB_CLIENT_CLOSED; and a key restricted to a subset of your sub-clients answers 403 ON_BEHALF_OF_NOT_ALLOWED_FOR_KEY for any node outside it.
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/partner/v1/network/connections/9c1f7a20-1a3b-4c8d-9e2f-0b5a6c7d8e9f"Allow a member to pay you POST
By their exact handle. Takes effect on the next settlement to you; nothing is asked of them. Adding a member already listed returns the existing row unchanged, so a retry is safe without an idempotency key.
Read the network profile GET
Your own, or — with x-on-behalf-of — that sub-client's. null when the node has not joined the network yet.