Changelog

• Every /v1 error response includes doc_url, a link to the page for its code, except for a request body that is too large or can’t be read, and for an Idempotency-Key replay of a response stored before this release. The new Errors tab explains each code and how to handle it.
• A missing required field now returns code: "parameter_missing". It previously returned a type-error code such as parameter_invalid_string.
• An invalid or missing X-Organization-Id header now reports parameter_invalid or parameter_missing for the header in invalid-params, matching the top-level code, instead of a generic validation_error.
• A value repeated within one request on POST /v1/contacts or POST /v1/entities now returns top-level code: "parameter_invalid", matching invalid-params, instead of validation_error.
• A request body that isn’t valid JSON now returns the Error object with code: "validation_error" instead of an HTML page.
• POST /v1/distributions for a vehicle with no bank account for payouts now returns 400 instead of 500, and an unknown vehicle returns a 400 field error instead of 500.
• A string longer than its maximum now returns parameter_invalid_string instead of parameter_invalid.

• Transaction — what each status, source.type and workflow.type means, the status lifecycle, and how reversals and returns appear. TransactionStatus, TransactionSource and TransactionWorkflow link to it.
• Object IDs — every ID prefix and the ID guarantees: IDs never change, and an object keeps its ID when it is updated.
• FinancialAccount — the account types and balance fields.
• List, Currency and IdempotencyKey — the conventions every endpoint shares.
• Distribution, DistributionPayment, PaymentInstructions, Entity, Contact, Organization and Vehicle.

• POST /v1/distributions creates and publishes exactly one distribution (the array must contain a single item). Its payments start as staged.
• Every endpoint can return 400, for example on a malformed path ID or X-Organization-Id header.
• Unknown entities or contacts on POST /v1/distributions return 400, not 404, and its 409 means the external_reference already exists.
• POST /v1/payment_instructions validates its input and can return 404 and 409.
• Every create lists the 409 returned while an earlier request with the same Idempotency-Key is still running, and 422 covers reusing a key for a different method, path or organization, not only a different body.
• X-Organization-Id is optional when the access token is bound to an organization or the integration can access only one.
• The id filter on transactions can’t be combined with after or before.
• An id filter on any list returns every match in one page and can’t be combined with page, page_before or limit, correcting the 1.10.0 note that pagination applies within the filtered set.
• Clarifies sender_payment_instructions_url and the deprecated list url.

​

timeless + timezone-less after + before filters

• DateOrDateTime
• ZonedDateTime
• UtcDateTime
• TimeZone

• wire - incoming or outgoing wire transfer
• ach - ach pull or push
• transfer - on-platform transfers between Nova-mangaged accounts
• other

Note on returns:

1. Initiating wire transfer (tx_1) completes (status: "completed")
2. Days later, tx_1 is rejected by the destination (status: "returned")
3. Return leg (tx_2``) is created and completes (status: “completed”`)

• sort_by=settled_at (default) or sort_by=created_at
• independently optional ISO 8601 after and before date bounds
• backward paging via previous_page_url
• repeated id filters (max 100), returning matches in one unpaginated page. transaction objects now include financial_account, updated_at, and workflow (the Nova activity, currently a distribution payment, that caused the transaction, or null for bank activity Nova did not initiate). The endpoint now allows up to 1000 transactions per page (default 100).