finance

Send Ar Scheduler Test

Send Test -- v1 parity: POST /drafts/:invoiceId/:step/test (ar-agent.ts:1560-1606). Deliberately bypasses app/platform/email_out.send_email's claim-once floor: a test send must NEVER consume the real ar:{invoice_id}:{cadence_step} idempotency slot (that would permanently block the real send for this invoice/step the moment someone clicked Test), matching v1's own test path (a bare sendGmailMessage call, no activity_log write at all) -- see app/modules/finance/ar_scheduler_send.py's send_test_email docstring.

A STUBBED SEND MUST NEVER PRESENT AS A DELIVERED ONE. build_ar_email_ sender returns StubEmailSender whenever any of its three gates is off -- ar_customer_email_enabled is false on production today, so this route's sender IS the stub right now. Before this build task the response was an unconditional {"ok": True} regardless: Frederick clicked Send Test and got exactly that, with no mail and no error.

post/api/finance/ar-scheduler/drafts/{invoice_id}/{step}/test

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/finance/ar-scheduler/drafts/{invoice_id}/{step}/test
  • Auth: none declared

Path parameters

invoice_idstring uuid required
stepstring required

Request body

test_emailstring required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.