Create Payment

POST

Query

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

The client receiving the payment.

stringrequired

The payment type identifier.

stringrequired

The payment date.

numberrequired

The payment amount.

objectrequired

Invoices to apply the payment to.

string

External transaction reference.

string

Internal payment notes.

Try this request

Request

curl --request POST \
  --url "https://connect.mindcloud.co/v1/universal/invoiceNinja/latest/actions/create-payment" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "clientId": "",
  "typeId": "",
  "date": "",
  "invoices": ""
}'

{
  "success": true,
  "data": [
    {
      "amount": 1,
      "applied": 1,
      "archivedAt": 1,
      "clientId": "string",
      "createdAt": 1,
      "currencyId": "string",
      "date": "string",
      "documents": [
        {}
      ],
      "exchangeRate": 1,
      "id": "string",
      "isDeleted": true,
      "isManual": true,
      "number": "string",
      "paymentables": [
        {}
      ],
      "privateNotes": "string",
      "refunded": 1,
      "statusId": "string",
      "transactionReference": "string",
      "typeId": "string",
      "updatedAt": 1
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.