Three credits per successful account
iCloud is priced at three credits per completed account in the current model. MailMaker calculates the total before the order starts.
MAILMAKER PROVIDER
iCloud account requests with cost and progress upfront.
Handle a higher-complexity provider inside the same interface and API contract used by the rest of your email account workflow.
Only successful iCloud accounts consume credits. A failed item is guaranteed to use zero credits, and any temporary reservation returns automatically.
Guarantee details →BUILT FOR
Where iCloud fits.
- Apple ecosystem testing
- Cross-platform email coverage
- Teams that need explicit cost controls
The same observable task model
Although the provider cost differs, iCloud orders use the same status lifecycle, task retrieval, result counts, and exports as other MailMaker providers.
iCloud covers Apple email, not managed Apple identity
Use iCloud for Apple ecosystem email-flow or cross-platform mailbox coverage. Do not treat the task as Apple Business Manager, managed Apple ID, device enrollment, or organization-level identity administration.
Three-credit pricing deserves a separate approval gate
Run the smallest representative iCloud pilot and reconcile it before increasing volume. Set both a quantity ceiling and a total credit ceiling; if either limit is reached, require a named approver to review the previous task and remaining balance.
Test the Apple email flow before approving another wave
A completed iCloud task should be checked against the Apple-oriented email or cross-platform mailbox flow that motivated it. Do not approve a larger three-credit batch until the receiving product accepts the pilot and the result owner confirms the handoff.
Failed-account credit protection
Only successfully completed iCloud accounts consume credits. Every item reported as failed is guaranteed to use zero credits; if 3 credits were reserved during processing, the reservation returns to the workspace automatically. A partial task is charged only for successful output.
Plan iCloud volume with real acceptance criteria
A representative pilot uses the real configuration, export format, owner, and downstream destination. At 3 credits per successful account, 10 completed results use 30 credits and 100 use 300. Scale only after the receiving workflow accepts the pilot and returned credits have been reconciled.
Keep the final record explainable
Preserve the iCloud task ID with requested, successful, and failed counts, actual credits used, credits returned, result owner, and export destination. If a replacement is approved, include only the unresolved quantity instead of repeating the completed portion of the original task.
ICLOUD QUESTIONS
Clear answers before an order starts.
Why does iCloud use more credits?−
MailMaker uses provider-specific pricing based on the relative complexity and infrastructure cost of each creation workflow.
Can iCloud orders be managed through the API?+
Yes. iCloud uses the same API task contract and status retrieval workflow as the other supported providers.
What happens when a iCloud account fails?+
The failed item consumes zero credits. Any credit reservation for that item is returned automatically, while successful items in the same task remain valid and chargeable.
Should I validate iCloud before ordering in bulk?+
Yes. Use a representative pilot with the real result owner, export format, and downstream destination before increasing quantity.
Review the cost. Run the task.
Start with iCloud selected and keep every result tied to a visible order.
Create iCloud accounts →