Preview Financial Line Type Impact
GET/api/veracore/integration-instances/:integration_instance/financial/preview-impact
Preview how many financial lines and sales orders would be affected if the fulfillment-cost financial line type configured on this Veracore integration instance were changed to new_type_id. This is a read-only computation — no data is modified.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
The preview compares the currently configured type against the proposed one for fulfillments in the warehouse linked to this instance:
rewire_lines— existing fulfillment-cost financial lines that would be moved from the old type to the new type.backfill_lines— fulfillments with a cost that have no financial line of the new type yet and would get one created.sales_orders_impacted— distinct sales orders touched by either change.is_noop—truewhen the change would have no effect (same type, no linked warehouse, or the proposed type is not a cost type).
Omit new_type_id (or send it empty) to preview clearing the setting.
Errors
404when the integration instance does not exist.422whennew_type_idis not an existing financial line type id.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.