Create a transaction

POST/accounting/{connection_id}/transaction

Parameters

fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Payload

idstring
created_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
memostring
total_amountnumber
negative for CREDIT, positive for DEBIT
tax_amountnumber
negative for CREDIT, positive for DEBIT
account_idstring
(reference to AccountingAccount)
referencestring
sub_total_amountnumber
split_account_idstring
payment_methodstring
payment_termsstring
customer_messagestring
typestring
eg. CreditCardCharge, Check, Invoice, ReceivePayment, JournalEntry, Bill, CreditCardCredit, VendorCredit, Credit, BillPaymentCheck, BillPaymentCreditCard, Charge, Transfer, Deposit, BANK_DEPOSIT, BANK_TRANSFER, Statement, BillableCharge, TimeActivity, CashPurchase, SalesReceipt, CreditMemo, CreditRefund, Estimate, InventoryQuantityAdjustment, PurchaseOrder, GlobalTaxPayment, GlobalTaxAdjustment, Service Tax Refund, Service Tax Gross Adjustment, Service Tax Reversal, Service Tax Defer, Service Tax Partial Utilisation
lineitems array
currencystring
contacts array
organization_idstring
category_idsstring array
(reference to AccountingCategory)
project_idstring
(reference to TaskProject)
transaction_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
exchange_ratenumber
Exchange rate to the base/home currency at the transaction date
status enum
Valid values:
"PENDING"
"POSTED"
"VOID"
"OTHER"
Posting state of the transaction

Returns

Response fieldTypeRequiredDescription
idstringNo
created_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
memostringNo
total_amountnumberNonegative for CREDIT, positive for DEBIT
tax_amountnumberNonegative for CREDIT, positive for DEBIT
account_idstringNo(reference to AccountingAccount)
referencestringNo
sub_total_amountnumberNo
split_account_idstringNo
payment_methodstringNo
payment_termsstringNo
customer_messagestringNo
typestringNoeg. CreditCardCharge, Check, Invoice, ReceivePayment, JournalEntry, Bill, CreditCardCredit, VendorCredit, Credit, BillPaymentCheck, BillPaymentCreditCard, Charge, Transfer, Deposit, BANK_DEPOSIT, BANK_TRANSFER, Statement, BillableCharge, TimeActivity, CashPurchase, SalesReceipt, CreditMemo, CreditRefund, Estimate, InventoryQuantityAdjustment, PurchaseOrder, GlobalTaxPayment, GlobalTaxAdjustment, Service Tax Refund, Service Tax Gross Adjustment, Service Tax Reversal, Service Tax Defer, Service Tax Partial Utilisation
lineitemsAccountingTransactionLineItem[]No
lineitems[].idstringNo
lineitems[].unit_quantitynumberNo
lineitems[].unit_amountnumberNo
lineitems[].total_amountnumberNowill be a positive value for a debit and negative for a credit
lineitems[].account_idstringNo(reference to AccountingAccount)
lineitems[].object_typestringNo
lineitems[].namestringNo
lineitems[].descriptionstringNo
lineitems[].category_idsstring[]No(reference to AccountingCategory)
lineitems[].taxrate_idstringNoref -> AccountingTaxrate applied to the line
currencystringNo
contactsAccountingTransactionContact[]No
contacts[].idstringYes
contacts[].is_customerbooleanNo
contacts[].is_supplierbooleanNo
organization_idstringNo
category_idsstring[]No(reference to AccountingCategory)
project_idstringNo(reference to TaskProject)
transaction_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
exchange_ratenumberNoExchange rate to the base/home currency at the transaction date
statusenumNoPosting state of the transaction Values: PENDING, POSTED, VOID, OTHER

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'POST',
  url: 'https://api.unified.to/accounting/5de520f96e439b002043d8dc/transaction',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?