Match transactions
Changed onMatching invoices or a payment to a bank transactions.
The API expects the id of the transaction along with either a comma separated list of invoice ids OR the payment id to associate the transaction to.
Example for matching a transaction to two invoices:
{"transactions":[{"id":"olejRl5ejN","invoice_ids":"JxboYBLegw,JxboYBLeXX"}]}
Example for matching a transaction and a paymente:
{"transactions":[{"id":"olejRl5ejN","payment_id":"JxboYBLeXf"}]}
Matching expenses.
You can match an existing expense within Invoice Ninja - or - create a new expense using the following:
{"transactions":[{"id":"open5pld7A","vendor_id":"gl9avJnaG1","ninja_category_id":""}]}
To match to an existing expense:
{"transactions":[{"id":"Jxbo2qKagw","expense_id":"7N1aMM1aWm"}]}
Request
- Base URLhttps://demo.invoiceninja.com
- Authnone declared. Required headers: X-API-TOKEN, X-Requested-With
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Replaces the default response index from data to a user specific string
ie.
?index=new_index
response is wrapped
{
'new_index' : [
.....
]
}
Headers
The API token to be used for authentication
Used to send the XMLHttpRequest header
Request body
Response
The Bulk Action response
Changes
- info
endpoint added
- info
- breaking
api path removed without deprecation
- breaking