Connect the work. Keep the mailing decision yours.

REST API

For software you control: prepare a PDF, upload it privately, request a price, submit the approved mailing, then read its status.

• Keep an account-bound API key on a trusted server.
• Render the finished PDF in your own application; IRIS does not generate the document through the API.
• Save one idempotency key per approved mailing so an uncertain response can be retried safely.

Authenticated remote MCP

For a client that supports remote Streamable HTTP and bearer authorization. Discover tools for preparing an upload, registering a document, quoting, submitting, and reading status.

• Every MCP request needs an IRIS key with the required account access and tool scopes.
• Your trusted code must transfer the actual PDF bytes; requesting an upload does not transfer a local file.
• Enforce human review before a paid submission. A connected assistant is not permission to mail.

Set up access and review

1. Create and verify your developer account. Add prepaid credits before submitting a paid order.
2. Use a scoped credential stored securely. Give preparation tools only the access they need; reserve submission access for the approved mailing step.
3. Show a person the actual PDF or postcard faces, both names and complete addresses, print options, current price, and purpose.
4. Requote and review again if details change. Save the approved payload and idempotency key, then retain the returned order ID.

Build the exception path

Handle an invalid PDF, missing address field, expired upload, rejected authentication, or insufficient credits before submission. The documentation describes errors and retry behavior.

When a submission response is uncertain, reconcile the existing intent using the saved key and unchanged payload. Read status after you have an order ID; missing tracking is not a reason to create a replacement order.