POST/counterparty/{userId}/counterparties/{counterpartyId}/instrument

Create Payment Instrument (Stablecoin - PYUSD)

Creates a PYUSD stablecoin withdrawal instrument for a counterparty.

Path variables

FieldTypeRequiredPossible valuesDescription
userIdstringRequired

Unique user ID.

counterpartyIdstringRequired

Unique counterparty ID.

Headers

FieldTypeRequiredPossible valuesDescription
session-tokenstringRequired

SessionToken obtained from the Create GMA Session endpoint. All secured endpoints require this header.

Request body

FieldTypeRequiredPossible valuesDescription
CurrencystringRequiredPYUSD

Stablecoin currency.

TransferTypestringRequiredSTABLECOIN_WITHDRAW

Transfer type.

CustomValuesobjectOptional{ Nickname, Address, Blockchain: ETH | SOLANA }

PYUSD instrument fields: Nickname, Address (wallet address), Blockchain. Retrieve the required fields for the corresponding transfer type from the Get Required Fields for Instruments endpoint.

Example request

{
  "Currency": "PYUSD",
  "TransferType": "STABLECOIN_WITHDRAW",
  "CustomValues": {
    "Nickname": "Test Stable Coin for Broker",
    "Address": "0x742d****...****f44e",
    "Blockchain": "SOLANA"
  }
}

Response

FieldTypePossible valuesDescription
ResponseCodeinteger200 | 201 | 204 | 301 | 400 | 401 | 403 | 404 | 410 | 422 | 500 | 503

API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized).

ResponseMessagestringSuccess | Created | NoContent | BadRequest | Unauthorized | Forbidden | NotFound | Gone | UnprocessableContent | ServerError | ResourceMoved | ServiceUnAvailable | UnProcessableEntity

Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome.

ResponseDataobjectPlease refer to below example for response body

ID of the newly created PYUSD stablecoin instrument.

Example response

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": "3723242474729549789"
}

Requires `session-token: {SessionToken}` from Create GMA Session. Use the same client IP as authentication.

Search guide books, endpoints, paths, or parameters

↑↓navigateopenEscclose