Create expectations

POST /api/v1/statement-transaction/create-expectations

Personal access token & O auth2

Bulk action create expectations for incoming statement transactions. Useful when a provider statement has historic transactions which Plannr has not generated the expectations for. The client and policy for this transactions must exist within Plannr.

Headers

• Authorization string
• Content-Type string
• Accept string
• X-PLANNR-ACCOUNT-UUID string

application/json

Body Required

• statement_transactions array[string] Required

  Array of unreconciled statement transactions to bulk create matching expectations.

Responses

• 204

POST /api/v1/statement-transaction/create-expectations

curl \
 --request POST 'https://api.plannrcrm.com/api/v1/statement-transaction/create-expectations' \
 --header "Authorization: Bearer {OAUTH_ACCESS_TOKEN or PERSONAL_ACCESS_TOKEN}" \
 --header "Content-Type: application/json" \
 --header "Accept: application/json" \
 --header "X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}" \
 --data '{"statement_transactions":["aa163562-7de3-4e5a-859c-3f053c013a30","ac93c8d8-fb5e-4201-b284-fd6cee8d9999"]}'

Request examples

# Headers
Authorization: Bearer {OAUTH_ACCESS_TOKEN or PERSONAL_ACCESS_TOKEN}
Content-Type: application/json
Accept: application/json
X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}

# Payload
{
  "statement_transactions": [
    "aa163562-7de3-4e5a-859c-3f053c013a30",
    "ac93c8d8-fb5e-4201-b284-fd6cee8d9999"
  ]
}