Frankly

Cancel delivery jobs not yet handed off. Inspect each returned status: in-flight messages cannot be recalled. The public post remains published. Requires deliveries:write.

cancel_delivery

Cancel a delivery preview without changing the public post. Requires deliveries:write.

discard_delivery_draft

Cancel an unpublished draft when requested. This cannot delete a published post. Requires posts:write.

discard_post_draft

Cancel an unpublished combined draft when requested. Creates no public post or delivery. Requires posts:write and deliveries:write.

discard_post_and_delivery_draft

Prepare an immutable ten-minute preview for one to five representatives. Show exact text, real-name author, recipients and public app/guest-feed visibility. Does not publish or send. Requires posts:write.

create_post_draft

Use when the person wants to contact or send a message to offices. Prepare one ten-minute preview showing exact text, real-name author, public app/guest-feed visibility, offices and the contact values shared with each office. Ask for ONE explicit approval covering publication, sending and contact sharing. Does not publish or send. Never silently fall back to publication-only if delivery is unavailable. Keep approval previews concise: show the exact message, selected offices and actual contact values shared with each office. Describe sending and contact sharing together, for example: "Send your message to the selected office with the contact details shown." Do not narrate transport protocols, fax mechanics, Firebase, PDF generation or internal queue schedules in routine approval text. Route metadata is operational context, not a checklist to recite. If asked how or when delivery happens, or if a requested deadline makes timing relevant, explain the actual route accurately; fax is processed through the existing weekly queue. Never promise immediate delivery. Preserve all public-visibility and contact-sharing disclosures and obtain explicit approval. Requires posts:write and deliveries:write.

create_post_and_delivery_draft

Prepare a separate ten-minute delivery preview for an existing post and up to five offices. Show exact message, recipients and shared contact values. Does not send. Keep approval previews concise: show the exact message, selected offices and actual contact values shared with each office. Describe sending and contact sharing together, for example: "Send your message to the selected office with the contact details shown." Do not narrate transport protocols, fax mechanics, Firebase, PDF generation or internal queue schedules in routine approval text. Route metadata is operational context, not a checklist to recite. If asked how or when delivery happens, or if a requested deadline makes timing relevant, explain the actual route accurately; fax is processed through the existing weekly queue. Never promise immediate delivery. Preserve all public-visibility and contact-sharing disclosures and obtain explicit approval. Requires deliveries:write.

create_delivery_draft

After ONE explicit approval of the complete combined preview, atomically publish and queue sending. The approval must cover exact text, real-name public app/guest-feed publication, offices and displayed contact sharing. Never default confirmed, publicationAccepted or sharingAccepted. Reuse idempotencyKey on retries. Waits briefly for the worker and returns the latest per-office result. Report each office’s recorded result: submitted means successfully submitted through its sending channel (CWC for House, SCWC for Senate); queued/processing means pending; unknown means unconfirmed. State failures and mixed outcomes clearly. For routine success confirmations, omit unsolicited office-receipt or read-status caveats. Never assert that a message was read or unread. If the user specifically asks about office receipt or reading, explain that this API reports channel submission and does not track those events. After publish_post or publish_and_send returns publication.status=published, add one brief optional invitation: "Continue the conversation in Frankly—explore posts, add a comment, and engage with others." Link to the returned appLinks.ios and appLinks.android as iPhone and Android, or just the relevant platform if already known. These are app-store links, not links to a specific post. Do not invent deep links, claim the post is already indexed, or repeat the invitation on status checks or retries. Keep the actual result first; omit the invitation if publication failed or the post was deleted. Requires posts:write and deliveries:write.

publish_and_send

Publish only after explicit approval of the exact preview and public real-name app/guest-feed publication. Never default confirmed or publicationAccepted. Use the same idempotencyKey on retries of the same action. Publication does not authorize delivery. After publish_post or publish_and_send returns publication.status=published, add one brief optional invitation: "Continue the conversation in Frankly—explore posts, add a comment, and engage with others." Link to the returned appLinks.ios and appLinks.android as iPhone and Android, or just the relevant platform if already known. These are app-store links, not links to a specific post. Do not invent deep links, claim the post is already indexed, or repeat the invitation on status checks or retries. Keep the actual result first; omit the invitation if publication failed or the post was deleted. Requires posts:write.

publish_post

Read the exact message and route-specific shared contact fields before requesting separate sending approval. Keep approval previews concise: show the exact message, selected offices and actual contact values shared with each office. Describe sending and contact sharing together, for example: "Send your message to the selected office with the contact details shown." Do not narrate transport protocols, fax mechanics, Firebase, PDF generation or internal queue schedules in routine approval text. Route metadata is operational context, not a checklist to recite. If asked how or when delivery happens, or if a requested deadline makes timing relevant, explain the actual route accurately; fax is processed through the existing weekly queue. Never promise immediate delivery. Preserve all public-visibility and contact-sharing disclosures and obtain explicit approval. Requires deliveries:write.

get_delivery_draft