Create forecasted transaction

post

https://api.atlar.com/analytics/v2beta/forecasted-transactions

Create a forecasted transaction.

Body Params

parent

required

All forecasted transactions must be associated with either an account or an entity.

amount

required

date

required

full-date notation as defined by RFC 3339, section 5.6, for example, 2017-07-21.

description

string

required

origin

object

The origin of this forecasted transaction, e.g. manual user input or AP/AR data.

counterparty

object

metadata

object | null

Optional key-value metadata. Set the cash-flow category with key atlar.category (e.g. {"atlar.category": "Sales"}); there is no separate category field.

externalId

string

^[a-zA-Z0-9._\-+=]{1,64}$

External ID is optional to use, but if used, the Atlar platform will persist it, index it, as well as require it to be unique across all resources. It is possible to retrieve a resource using the external ID using the prefix external:.

Responses

201The created forecasted transaction.

400Bad request.

409Conflict.