Create transaction

Transactions API · transactions.create

URL · Fields · Example · Response · Try it

URL and authentication

POST https://YOUR-BACKEND/api/automation/v1/execute

Send Authorization: Bearer <connection key>, Accept: application/json and Content-Type: application/json. Create a connection.

This operation requires write access and CRM permission add_transaction. The gateway invokes POST /api/v1/app/transactions internally. Use the POST URL above with your automation key, including for read and delete operations.

Request parameters

Fields

Internal transactions require internal_listing_id and cannot include external_client. For external_listing, internal_listing_id and external_client must be empty, and external_listing must include company, listing_type and agent.name/phone/email. external_client fields are optional for external_client transactions. A transaction cannot be created as cancelled. Rental transactions with payment_method cheque require at least one cheque, unique cheque numbers and a total matching transaction_amount within 0.01. Cheques cannot be supplied for a sale.

Fields below belong inside data. Dot paths describe nested objects; * means each array item. nullable permits null and sometimes validates a supplied field. in: lists allowed values; min: and max: limit the value, length or item count. exists: and exists_in_company: require a valid record ID. Conditional rules such as required_if and required_with refer to other fields in the same payload. Use YYYY-MM-DD for date-only values and timestamps with timezone offsets for follow-ups.

Example request

Replace the example IDs and values with records in your installation. Supply any additional custom fields required by your company.

{
  "operation": "transactions.create",
  "data": {
    "transaction_source": "internal",
    "internal_listing_id": 1,
    "company_role": "listing_agent",
    "transaction_type": "sale",
    "transaction_amount": 1000000,
    "commission_rate": 2,
    "commission_amount": 20000,
    "transaction_date": "2026-11-01",
    "commission_splits": [
      {
        "recipient_role": "listing_agent",
        "internal_agent_id": 1,
        "split_percentage": 100,
        "split_amount": 20000
      }
    ]
  },
  "idempotency_key": "example-event-12345"
}

Response

Returns the created transaction in data. Use data.id for subsequent requests. Related fields depend on the resource and your permissions.

The gateway preserves the underlying HTTP status and JSON body. Successful requests return HTTP 200. A response may also include localized message fields.

Illustrative response excerpt (additional fields may be returned):

{
  "status": "success",
  "data": {
    "id": 456
  }
}

Errors

Validation failures may return message / errors, or an error string with an optional fields array. The tester shows the actual HTTP status and full body. Read about limits and retries.

Try it

An idempotency key of 8–100 characters is required for writes. Reuse it only for an identical retry.