Update a bankfeedtransaction

PUT/accounting/{connection_id}/bankfeedtransaction/{id}

Parameters

Payload

idstring

created_atdate-time

creation timestamp, in ISO 8601 format and UTC (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

updated_atdate-time

last-update timestamp, in ISO 8601 format and UTC (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

organization_idstring

ref -> accounting Organization this record belongs to

bankfeedaccount_idstring

ref -> BankfeedAccount this transaction belongs to

transaction_atdate-time

when the transaction occurred (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

posted_atdate-time

when it posted / cleared (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

amountnumber

transaction amount (positive; direction from type)

type enum

Valid values:

"DEBIT"

"CREDIT"

direction: DEBIT, CREDIT

bank_categorystring

the bank's own category label

descriptionstring

bank memo / statement text

merchant_namestring

counterparty as reported by the bank

is_pendingboolean

true if not yet cleared

referencestring

bank reference or check number

currencystring

ISO 4217

contact_idstring

matched vendor/customer once reconciled (reference to AccountingContact)

account_idstring

GL account once categorized (reference to AccountingAccount)

category_idsstring array

dimension refs -> AccountingCategory (class/department/location)

raw

The original data from the integration's API

Returns

AccountingBankfeedtransaction

Response field	Type	Required	Description
`id`	string	No
`created_at`	string (date-time)	No	creation timestamp, in ISO 8601 format and UTC (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
`updated_at`	string (date-time)	No	last-update timestamp, in ISO 8601 format and UTC (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
`organization_id`	string	No	ref -> accounting Organization this record belongs to
`bankfeedaccount_id`	string	No	ref -> BankfeedAccount this transaction belongs to
`transaction_at`	string (date-time)	No	when the transaction occurred (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
`posted_at`	string (date-time)	No	when it posted / cleared (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
`amount`	number	No	transaction amount (positive; direction from type)
`type`	enum	No	direction: DEBIT, CREDIT Values: `DEBIT`, `CREDIT`
`bank_category`	string	No	the bank's own category label
`description`	string	No	bank memo / statement text
`merchant_name`	string	No	counterparty as reported by the bank
`is_pending`	boolean	No	true if not yet cleared
`reference`	string	No	bank reference or check number
`currency`	string	No	ISO 4217
`contact_id`	string	No	matched vendor/customer once reconciled (reference to AccountingContact)
`account_id`	string	No	GL account once categorized (reference to AccountingAccount)
`category_ids`	string[]	No	dimension refs -> AccountingCategory (class/department/location)

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"
}

Status	Error	Meaning
`400`	Bad Request	The request was malformed or failed validation.
`401`	Unauthorized	The connection is likely broken; re-authorize it.
`403`	Forbidden	The connection is missing permissions or scopes.
`404`	Not Found	The requested resource does not exist.
`429`	Too Many Requests	Rate limit exceeded (see the two sources below).
`500`	Internal Server Error	An unexpected error occurred.
`501`	Not Implemented	Not 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: 'PUT',
  url: 'https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);

Code Samples

Node.js SDK

import { UnifiedTo } from '@unified-api/typescript-sdk';

const sdk = new UnifiedTo({
    security: {
        jwt: '<YOUR_API_KEY_HERE>',
    },
});

const connectionId = '5de520f96e439b002043d8dc';

const id = '1234';

const results = await sdk.accounting.updateAccountingBankfeedtransaction({ connectionId, id, accountingBankfeedtransaction: { }, 
    fields: '',
    raw: '',
 });

Node.js (axios)

const options = {
  method: 'PUT',
  url: 'https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);

Java

AsyncHttpClient client = new DefaultAsyncHttpClient();

client.prepare("PUT", "https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw=")
  .setHeader("accept", "application/json")
  .setHeader("authorization", ".....")
  .execute()
  .toCompletableFuture()
  .thenAccept(System.out::println)
  .join();

client.close();

Go

import (
	"fmt"
	"net/http"
	"io/ioutil"
)

url := `https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw=

req, _ := http.NewRequest("PUT", url, nil)

req.Header.Add("accept", "application/json")
req.Header.Add("authorization", ".....")

res, _ := http.DefaultClient.Do(req)

defer res.Body.Close()
body, _ := ioutil.ReadAll(res.Body)

Python

import requests

url = "https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw="

headers = {
    "accept": "application/json",
    "authorization": "....."
}

response = requests.put(url, headers=headers)

PHP

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw=",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "PUT",
  CURLOPT_HTTPHEADER => [
    "accept: application/json",
    "authorization: ....."
  ],
]);

Ruby

require 'uri'
require 'net/http'
require 'openssl'

url = URI("https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw=")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Put.new(url)
request["accept"] = 'application/json'
request["authorization"] = '....'

response = http.request(request)
puts response.read_body

cURL

curl --request PUT \
  --url 'https://api.unified.to/accounting/5de520f96e439b002043d8dc/bankfeedtransaction/5de520f96e439b002043d8d8?fields=&raw=' \
  --header 'accept: application/json' \
  --header 'authorization: .....'

Are we missing anything? Let us know

Was this page helpful?