transactions

Create Counterpart

Changed on Nov 5, 2026

Mark a transaction as a transfer by auto-creating its counterpart in another (typically manual) account.

post/api/transactions/{transaction_id}/create-counterpart

Request

Base URL
https://demo.usesecuro.com (the document declares no server; this is the origin it was published from)
Auth
OAuth 2
Password
Token URL/api/auth/login
TypeScript
https://skmtc.dev/usesecuro/apis/securo/docs/api/transactions/:transaction_id/create-counterpart/post.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

transaction_idstring uuid required

Headers

X-Workspace-Idstring nullable

Request body

to_account_idstring uuid required

Response

Successful Response

transfer_pair_idstring uuid required

Changes

Nov 5, 2026416a7752fec4 Revision changes
- info
  added the optional property /// to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property /// to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  added the optional property / to the response with the status
- info
  the / response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the // response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the /// response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the //// response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the // response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the / response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the // response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the /// response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the //// response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status
- info
  the // response's property pattern ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ was removed for the status

Operation history