Amendment and Renewal Approvals

​

How it differs from a new-business quote

​

Lifecycle

​

The proposal card

​

Requesting approval

1. Open the draft amendment or renewal quote. When its terms match a rule, the card shows Request approval instead of Send for signature.
2. Review why. Each product row that triggers a rule is highlighted with the rule name and the reason, for example Discount above 20%: Product A: discount 25% → 35%; above 20% and worsens. Rows that changed but trigger nothing are shown without the highlight. On a renewal the reason names the level rather than the change, for example Product A: discount 25%; above 20%.
3. Select Request approval. The dialog repeats the reason and the comparison, asks for a justification when the ruleset requires one, and, when the ruleset lets the requester choose, asks what should happen after approval.

​

While a quote waits

• No document is issued. There is no signing link and no PDF for the customer. A shared link to the quote says it still needs approval and offers no signing.
• The terms are locked. Changing prices, discounts, quantities or products is refused with a prompt to return the quote to draft first. Delivery details such as the quote’s name can still change, and the request stays pending.
• The subscription stays active. It keeps billing on its current terms.
• Other changes to the subscription wait. A second amendment quote, a new draft version of the subscription, a self-service plan change by the customer and a scheduled price escalation are all refused while the quote holds the subscription, with a message that names the open quote.
• A change to the live terms still goes through, and makes the approval stale. If someone edits the subscription’s current terms while the request waits, the approval no longer matches what the customer would sign. When the approver decides, the quote shows Needs review instead of being sent, and the comparison is shown against the new terms. Return it to draft and request approval again.

​

Reviewing a request

​

After a decision

​

Approved

• Automatic — the quote is sent for signature as soon as the flow is approved.
• Manual — the quote shows Approved and waits. A rep selects Send for signature when ready.

​

Rejected

​

Editing a quote that is out for signature

​

Signing

• A quote in Awaiting approval, Rejected or Needs review cannot be signed, whether through the hosted signing page or by marking it signed offline.
• When the customer signs an approved, issued quote, the change is applied to the subscription as for any amendment quote.
• Signing or applying the same quote twice is refused; the change is applied once.

​

Renewals and automations

• The quote is kept in Pending approval with an approval request, and waits for the approvers’ decision.
• The automation step reports the pending approval as its failure and is not retried. Running the same automation run again returns the same quote and the same approval request rather than creating another.
• An activate_quote step on a quote that is waiting for approval fails and changes nothing.

​

When rules change

• Editing a rule re-evaluates requests that are still waiting. Each is replaced by a new version of the request, evaluated against the edited rule, and stays pending. The request’s generation in the API increases.
• Disabling a rule or ruleset releases the requests that only it required.

​

Public API

• Quote status. A quote waiting for approval has status pending_approval. List quotes filters by status, kind and subscription_id.
• The approval object. Get a quote returns approval with the request’s status, operation, flow_id, generation, requested_at and decided_at. On an amendment or renewal quote it describes the approval of the quote’s own issuance. Its status is one of none, pending, approved_manual_hold, approved_awaiting_execution, executed, failed, stale, rejected or canceled; stale is the API’s name for Needs review.
• Refusals. Create a quote for an amendment, Send a quote for signature and Mark a quote as signed offline fail when issuing needs approval. The error’s approval object names the pending flow in approval.flow_id and why the call was refused in approval.reason. Repeating the call while the approval is pending returns the same flow.

curl "https://api.alguna.io/quotes?kind=amendment&status=pending_approval" \
  -H "Authorization: Bearer $ALGUNA_API_KEY" \
  -H "Alguna-Version: 2026-04-01"

import os
import requests

response = requests.get(
    "https://api.alguna.io/quotes",
    params={"kind": "amendment", "status": "pending_approval"},
    headers={
        "Authorization": f"Bearer {os.environ['ALGUNA_API_KEY']}",
        "Alguna-Version": "2026-04-01",
    },
)
response.raise_for_status()
for quote in response.json()["data"]:
    print(quote["id"], quote["approval"]["status"])

​

Troubleshooting

​

Next steps