POSTing split transactions

Do you have an example of creating a new transaction that is split? I've tried several things through the API, but nothing seems to work. Is this supported? If not, do you have a timeline for it? If it is supported, can we have an example json that works? Thanks!

46replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Split transactions are now supported!  You can specify a "subtransactions" array when creating or updating a transaction like this:

    curl -H "Authorization: Bearer $API_ACCESS_TOKEN" -H "Content-Type: application/json" -X POST --data-binary @- << EOF
          "memo":"This is a split",
                "payee_name":"Split payee",
                "memo":"Split 1"
                "memo":"Split 2"

    See the API Endpoint Documentation for more details.

    The client libraries have not been updated to support splits yet, but will be in the near future.

    Like 4
      • Alfred
      • firnnauriel
      • 1 mth ago
      • 1
      • Reported - view

      Brady Fantastic news! I'll test it sometime this week. Thanks for the work.

      Like 1
    • Brady Cool. But I‘m not able to create a transaction with a transfer as a subtransaction. I tried with payee_name and payee_id. But the subtransaction has no payee in the end.

      Can you give a hint, or is there a bug?

    • Pink Yearling Per the docs, transfer payees are not allowed for splits.

  • Nice! Thanks Brady!

    Like 1
  • So excited for this! Thank you! 

    Like 1
  • Integrated split transactions into my grocery store receipt processor and it's working great. Thanks again!

    Like 2
  • Hi Brady, nice to see this feature!
    But there is a problem - why subtransactions cannot be specified for an imported transaction?
    I'm heavily relying on this field to backtrack created transactions.

  • Gold Wrench - There is a technical design reason we don't support that, currently.  One thing you could do is create a regular non-imported transaction (no import_id) as a split and then create a secondary imported transaction that will match (same account_id, amount, and date) to that first transaction.  The net result would be a single, split transaction with a matched, non-visible imported transaction counterpart.  This is effectively how things work when not using the API.

    • Brady thank you, will try it out!

Like16 Follow
  • 3 wk agoLast active
  • 46Replies
  • 1490Views
  • 32 Following