Questions about Apple Books Delivery

Authors and small publishers can deliver a book they own in Junifye to their own Apple Books provider account. You remain the publisher, and Apple pays your account directly; Publifye supplies the delivery workflow. You need your own eligible Apple account and credentials, and Apple still decides whether to accept the book.

Ask your AI

Help me deliver my Junifye book to my own Apple Books account.

What it does

operator_guide → apple_ready → apple_allowance → apple_credential_set → apple_delivery_begin → (secure HTTPS upload) → review → apple_deliver

What you get

A delivery job on your own account, with progress and evidence.

A dry run lets a cautious first-time author validate a package without uploading it to Apple. Open a delivery with request_type=verify, supply the required files securely, and submit it for verification. A dry run does not spend a delivery allowance; Apple acceptance remains a separate decision.

Ask your AI

Check this book for delivery problems without publishing it.

What it does

apple_ready → apple_delivery_begin (request_type=verify) → secure upload → apple_deliver → apple_delivery_status

What you get

A verification result explaining anything that would stop the book, with no upload to Apple.

A press can prepare and submit separate owner-bound jobs for its books, then follow each job to its result. Apple Transporter work runs one at a time across the service, so a backlist progresses through the queue rather than uploading all at once. Check your allowance first and arrange larger volumes through the store or contact page.

Ask your AI

Help our press deliver these books and track each result.

What it does

apple_allowance → for each book: apple_delivery_begin → review → apple_deliver → apple_delivery_status

What you get

One auditable job per book: queued, uploaded and seen by Apple kept apart.

You can preview how a chosen base price expands into Apple territory tiers before submitting an upload. The result includes the territory rows and identifies refusals or missing pricing inputs. Previewing does not upload a book or change its Apple listing.

Ask your AI

Preview the Apple territory prices for this book before I approve delivery.

What it does

apple_price_preview (book_id, base_price_usd)

What you get

A territory price table, with gaps and refusals shown rather than guessed.

Your AI can inspect the job state and safe delivery progress instead of guessing why a book stopped. The service distinguishes an upload result from a later Apple lookup, so a delayed confirmation is not a reason to send the same upload again. Private credential material and raw Transporter diagnostics are not ordinary customer progress.

Ask your AI

Find out what stopped this delivery and what I can safely do next.

What it does

apple_delivery_status → apple_delivery_log → follow the named refusal or review

What you get

The saved state and a concrete next step.

An authorized internal publishing operator can reconcile a supplied ISBN list with Apple and read the saved results. This is not an unrestricted Apple catalogue listing: the answer is bounded by the identifiers supplied. Catalogue scans are administrator operations, so customer OAuth users should ask their publishing operator for this workflow.

Tell your AI, “Help me connect my Publifye account to Apple Books Delivery.” Add the MCP endpoint from the Connect page and sign in, then have the AI read operator_guide and call apple_connection_setup. You get the configured HTTPS submission routes and authentication guidance; Apple usernames, passwords and private-key bytes never belong in chat or MCP arguments.

Say, “Deliver this Junifye book to my Apple Books account.” Your AI reads operator_guide, checks apple_ready and apple_allowance, registers your App Store Connect credential identifiers with apple_credential_set, and opens apple_delivery_begin. A secure client uploads the requested files and per-job key over authenticated HTTPS; after the required reviews, apple_deliver submits the job and apple_delivery_status follows it. You need your own Apple account, the correct team or individual key type, and the provider confirmation requested by the workflow.

Ask, “Run a dry check on this book before publishing it.” Your AI checks apple_ready, opens apple_delivery_begin with request_type=verify, and has a secure client upload the required files and key; apple_deliver starts verification and apple_delivery_status returns the result. The pipeline checks the EPUB and its agreement with the book metadata, builds the delivery package and validates it before any upload. A clean check is useful evidence, not a promise of Apple acceptance.

Say, “Follow this delivery and tell me what has actually happened.” Your AI polls apple_delivery_status and reads apple_delivery_log for safe progress; uploads share a single Transporter slot, so queued work is normal. The result keeps upload evidence separate from later lookup evidence, and a lookup does not prove Apple review or storefront availability. You get an honest state to act on, rather than a guessed completion time or an automatic duplicate upload.

Ask, “Show me the open Apple tickets for this book.” Your AI calls apple_connection_setup and apple_connection_status; an explicitly saved Books connection must be available for the operation. After you submit the attested app-specific password through authenticated HTTPS, apple_tickets_enqueue starts the owner-bound query, apple_ticket_job follows it and apple_ticket_page reads saved ticket results. You get the saved open tickets and notes; unavailable credentials or failed Apple queries are errors, not proof that there are no tickets.

Your App Store Connect key (.p8) is sent over HTTPS for one delivery job, kept only in that job's temporary workspace and destroyed when the job ends. A Books connection is different: it keeps your Apple username and app-specific password encrypted for its lifetime — 12 hours by default, at most 72 — and then deletes them. You can disconnect sooner, and you can revoke the app-specific password in your Apple Account settings at any time.

Delivery routing is derived from the book’s authoritative owner and stored provider binding, rather than chosen as a destination by a caller. The workflow checks the provider confirmation and credential binding and refuses missing or conflicting identity. Reviews bind the intended package, and later Apple observations are recorded separately from the upload result.

The service retains credential identifiers, key fingerprints and permanent delivery evidence so an attempted upload can be traced to its owner, book and package. A SHA-256 fingerprint identifies a key without recreating it; it is not a substitute for the encrypted credentials of an active saved Books connection. Job records, safe progress, saved tickets and reusable Books credentials have distinct lifetimes, and deleting credentials does not erase delivery evidence.

See the store for the current offer and arrange larger volumes through the contact page. Use apple_allowance with a book you own to inspect your allowance before submitting work. Delivery accounting distinguishes successful uploads from refused or failed work; verification, status reads and price previews do not spend a delivery. An uncertain upload must be investigated, not automatically retried or treated as proof that nothing was sent.

The books were delivered to your Apple provider account, so stopping this delivery service does not transfer them to Publifye. Apple remains responsible for its review and storefront decisions, and you continue to manage your own account. See the store and the linked service terms for the current purchase, cancellation and refund conditions; this service does not promise uninterrupted availability or a delivery deadline.