Documentation / Getting started
Packages & webhooks
Download validated assets and receive signed notifications when renders finish.
Packages and limits
Packages contain fastlane/screenshots/LOCALE for iOS and fastlane/metadata/android/LOCALE/images for Google Play, plus manifest.json and checksums.sha256. Files have store-specific names, exact dimensions, valid PNG encoding, no transparency and SHA-256 checksums.
A job supports up to 40 languages and 800 files; each iOS format has at most 10 screens, each Android format at most 8. Export packages expire after 30 days. Capture uploads use the existing project asset limits.
Structural validation cannot judge translation quality, clipping or store policy acceptance. Review localized outputs before store upload. Each manifest identifies the project, variant, export input and renderer. Updating project assets can affect subsequent reads; keep CI writes and exports in sequence.
Reliable automation
List projects and renders with limit (1–100) and opaque cursor. Follow data.nextCursor until null. Project collections require projectId.
Render states are queued, dispatching, rendering, succeeded, failed, cancelled and indeterminate. Only queued jobs can be cancelled. An indeterminate dispatch may already be running: retain its job ID and contact support instead of submitting another paid job.
Register HTTPS webhooks through /webhooks for render.succeeded and render.failed. Verify Webhook-Signature as HMAC-SHA256 of Webhook-Timestamp + "." + rawBody, using the returned secret. Reject timestamps older than five minutes, compare signatures in constant time, and deduplicate Webhook-Id. Delivery is at least once, with up to eight attempts and exponential backoff. A webhook is a notification; fetch the authoritative render status before acting.