Skip to main content

Approve or reject a corporate action plan

How a second operator approves or rejects a stored corporate action plan before confirm, and which action types an organisation can send for approval.

An organisation can require a second operator to approve a stored corporate action plan before confirm runs. See Corporate actions for the create, preview, and confirm sequence.

Approve or reject a plan

Enabling the corporate-actions row in the organisation's approval policy requires a second operator before confirm on irreversible actions: partialRedemption, stockSplit (forward or reverse), rightsIssue, capitalDecrease, coordinatedDistribution, buyback (with a cash leg or enabled under the gate), cash or in-kind cashDividend and distribution, and in-kind bondCoupon.

Every record includes an approval block:

Field
Meaning
policy
required, not_required, or not_applicable.
state
pending, approved, denied, expired, not_required, or not_applicable.
proposerUserId, lastPreviewedBy
Users who opened the approval or last previewed the plan. Neither can approve it.
planDigest
Hash of the stored plan that the checker echoes back in reviewedDigest.
approvedByViewer
true once the caller's own approval is recorded on the current request.
approvalsNeeded
Remaining approvals needed for multi-approver policies, or null when not pending.

Non-staff callers (without governance or supplyManagement, organisation owner, or platform administrator roles) read only announced records, with internal actor fields returned as null and approvedByViewer as false (Who reads which records).

Submit a decision

After preview, a different operator reads the plan and posts planDigest as reviewedDigest to POST /api/v2/tokens/{assetId}/corporate-actions/{corporateActionId}/decisions:

curl -sS -X POST "$DALP_API_URL/api/v2/tokens/$ASSET_ID/corporate-actions/$CORPORATE_ACTION_ID/decisions" \
  -H "X-Api-Key: $DALP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "decision": "approve",
    "reviewedDigest": "3b8f1d2c4a5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6e7f8"
  }'
  • Approve: Moves the record to approved (once approvalsNeeded reaches zero) so confirm can execute. Refused if the digest is stale or payingTreasury lacks cash-leg funding.
  • Reject: Requires a non-empty reason and ends the record in aborted (via releasing if custodial contracts were frozen) with approval.state: "denied".
  • Step-up: Session-authenticated decisions require walletVerification, while API-key decisions do not.
  • Cash dividends and distributions: Rejecting or acting after expiry first cancels the on-chain dividend using the checker's governance wallet. If cancellation fails or stays queued, the record stays previewed and returns 409 CORPORATE_ACTION_DIVIDEND_DECLARED (data.dividendId).

Decisions must satisfy the checker rules in Approve a corporate action. Refused decisions return DALP-12165 naming the rule in data.violation.

Expired windows and drift refusals

A decision arriving after the approval window closes (or a new create on the same token) ends the lapsed record in aborted (or releasing) with approval.state: "expired". On cash dividends and distributions, the dividend cancels first using that caller's wallet proof. Reads never send transactions, so an untouched lapsed dividend stays previewed until cancelled.

Confirm returns DALP-12052 when no confirmable preview exists (for example, a drafted record or a cash dividend confirm missing its preview root and totals).

Confirm returns 409 CORPORATE_ACTION_SNAPSHOT_DRIFT (DALP-12056) if balances moved on a call: "all" buyback or rights exercises moved on a rights close, and 409 CORPORATE_ACTION_PREVIEW_MISMATCH (DALP-12053) if a stock split's reference price moved. Re-preview a previewed record, or abort an approved record and raise a new action (using followsUpOn if a rights close already minted shares).

Policy configuration and waivers

Configure the gate via PUT /api/v2/operations/approval-policy (the corporate-actions row, also mapped to CORPORATE_ACTION_MAKER_CHECKER_ENABLED). It starts off. Disabling it requires wallet verification and, if Administration approvals are active, a second owner or platform administrator.

When the row is off (organization-disabled) or no second owner exists (too-few-approvers), records open with policy: "not_required" and waiver set. Confirm rechecks eligibility (except on cash dividends and distributions, which retain their waiver) and opens a pending decision if the organisation can now staff the gate.

For partial redemptions with a cash leg (denominationAsset, pricePerUnit, payingTreasury), see Tradable rights, cash legs and issuer calls.

Was this page helpful?