DealSleek API · Billing

Preview

Void Invoice

Void an invoice (→ VOID terminal).

POST/api/v1/billing/dispatch

Authorization

Minimum role
FinanceThe caller must hold this role or a higher one.
Action
VOID_INVOICE

Headers

  • AuthorizationstringRequired

    Access token of the signed-in user, as a Bearer token. It identifies the user, their role and the workspace.

  • X-CQRS-ActionstringRequired

    Names the command to run. Must be VOID_INVOICE for this endpoint.

  • Content-TypestringRequired

    Always application/json.

  • X-Idempotency-KeystringOptional

    A key you choose that is unique to this attempt. A command repeated with the same key is not applied a second time.

  • X-Correlation-IdstringOptional

    Your own identifier for the request. Returned in the x-correlation-id response header; generated when you leave it out.

Request body

  • current_statusenumRequired

    Invoice lifecycle. Dunning progress lives in billing_invoices.dunning_stage (DunningStage), not here: the former Dunning1/Dunning2 variants had no writer and no entry in the invoice transition table, so an invoice that ever reached them could not be paid, voided, or written off.

    Allowed values
    • DRAFT
    • OPEN
    • PAST_DUE
    • PAID
    • VOID
    • UNCOLLECTIBLE
  • invoice_iduuidRequired

    No description yet.

  • expected_versioninteger or nullOptional

    CORE invariant: mutations carry the version they read. Absent preserves legacy callers.

Response

Status 202. The command was applied. The body reports the outcome and, where the command changes a record, that record's new state.

  • successbooleanRequired

    true when the command was applied.

  • error_messagestringRequired

    Empty when the command was applied.

  • projected_stateobjectOptional

    The record as it stands after the command.

  • event_payloadobjectOptional

    The event the command recorded.

  • insightsarray of objectOptional

    Advisory notes about the result. Each has a code, a message and an impact number.

Errors

Every error carries an HTTP status. Where it also carries a code, branch on the code, not on the message.

  • 400X-CQRS-Action is missing or names a command this route does not accept. Send VOID_INVOICE.
  • 400DOMAIN_ROUTINGThe body is not a valid command. Check the required fields and their types.
  • 401The access token is missing, expired or not valid.
  • 401L1_AUTHThe caller's role is below finance or the caller has no access to this record.
  • 403L1_POLICYA business rule refused the command. The message names the rule.
  • 409L1_VERSIONexpected_version is not the record's current version. Read the record again, then retry.
  • 409L1_IDEMPOTENCYA command with this idempotency key was already applied.
  • 409CONFLICTThe command would duplicate a record that must be unique.
  • 500L3_COMMITThe command was valid but could not be saved.
Generated from the API contract · revision 007b75ac0754a359