Certified Mail API & SFTP
For recurring mailings, API and SFTP automation can reduce rekeying and move approved documents and recipient data from your system into mailing operations. The right setup is job-specific, so the published path starts with scoping, sample data, proof review and testing.
API
The published service describes using an API for direct integration, label creation, tracking and Return Receipt access. Endpoint paths, request schemas, authentication details and response/error codes are not publicly specified on the service page. Request current technical documentation from support before implementation.
SFTP
SFTP is the published secure file-transfer option for recurring or batch data. Setup includes job-specific credentials, an agreed file structure, sample files and a proof review before the automation is turned on.
Authentication: SFTP credentials are set up during the job configuration. API authentication is not documented publicly; request the current mechanism rather than assuming a bearer token or key format.
Secure transfer: the published page describes encrypted SFTP file transfers. Confirm credential handling, IP access and retention expectations during onboarding.
No guessed error codes: file validation, rejection details, retry behavior and status callbacks depend on the specific job setup. Include these questions in your technical kickoff.
A setup sequence to plan for
Treat this as a proofed mailing job—not a generic endpoint you can wire up without a shared data contract.
STEP 01
Contact support with your account needs, source system, mailing volume, selected services and a representative data file. For SFTP, the published setup process begins with a Custom Work Order and job-specific instructions.
STEP 02
Define how the source document and recipient data map to the approved job. For SFTP, support configures credentials and folder structure. Protect credentials and use the secure transfer path your team is given.
STEP 03
Submit sample data, inspect the generated proof and approve it. The published SFTP setup allows an end-to-end test of 10 records or fewer after approval.
STEP 04
After the workflow is enabled, submit approved files and reconcile them against the reports. Review exceptions and match USPS tracking to the internal recipient or case reference.
Workflow state vs USPS mailing state
The following are useful checkpoints to define with support. They are planning labels, not published API status strings or guaranteed callback events.
Custom Work Order accepted; sample data, IP and job details supplied.
Review the output, recipient mapping, print layout and mailing settings.
End-to-end test accepted by your team before live processing.
For each mailpiece, review USPS acceptance scan, tracking events and available delivery reports.
The service describes centralized tracking, confirmation reports and access to mailing evidence. Its SFTP instructions say files in the SFTP folder, including RRE signature reports, are available for 180 days. The account archive is described separately as a 10-year record archive. Ask support which report formats, retention rules and retrieval paths apply to your specific integration.
The published service states these tools have no extra integration fee; mailing charges still apply.
Published SFTP setup instructions say funds must be available before mailing begins. Confirm payment and funding arrangements for your account.
Assign owners for source-data approval, proof review, production release, exception handling and record reconciliation before go-live.
Next step
Share your current workflow, volumes, files and status requirements. Support can outline the job-specific setup and testing steps.
