Connect your listing video workflow

Upload your own photos, authorize a paid video, and follow its progress through a scoped API key. Review the resulting video in ReeltyPro before sharing it.

API access depends on the current rollout and video pipeline readiness. A specification does not mean every product is available. Check capabilities and the response to each request.

Account and permissions

Sign in with a verified email, open Account → Integrations, and create a key with only the permissions you need. Save it in your integration’s secure credential store. Never paste a key into prompts, URLs or source code. Keys expire after 90 days and can be revoked in Account.

• uploads:write starts and uploads your paid listing photo batches.
• videos:write uses your current eligible personal or team credit balance under existing member limits.
• videos:read reads your videos, source previews and verified released downloads.

Authorization: Bearer YOUR_REELTYPRO_API_KEY
Content-Type: application/json

From photos to a reviewed video

1. Check capabilities. GET /api/v1/capabilities returns current video readiness, photo limits and the exact photo rights statement.
2. Start a paid upload. POST /api/v1/uploads/start with a fresh UUID as upload_request_id. Reuse that UUID on retries. Eligible existing balance and storage capacity are required before photos enter the pipeline.
3. Upload 3–6 original photos. POST multipart requests to /api/v1/uploads/photos. Each request carries photo, folder=listings, photo_index starting at 1, and paid_batch as the JSON string returned by start. Send X-Reelty-Paid-Batch-Id with the batch ID. Save each returned URL and signed capability in order. Retry the same index with identical bytes.
4. Authorize the paid video. POST /api/v1/videos with your photo URLs, capabilities, listing reference, style and explicit video type. Send a new Idempotency-Key UUID and retain it. Set confirm_credit_use:true only after the user authorizes this spend, and supply the rights statement they affirmed for these photos.
5. Review in the app. Save jobId and poll its statusUrl no more than once every five seconds. Open reviewUrl for any candidate selection, final review and checking property facts. Downloads appear only through the existing release rules. This API cannot approve, schedule or publish a video.

Photo rights and product choices

The person supplying the photos must affirm:

I have the right to use these photos to market this property.

Choose standard for original-photo effects, ai_depth for the existing all-scene depth workflow, or selected_highlights with one or two explicitly selected source indices. These use their existing funded products and readiness checks. Standard effects are not generative AI. Do not replace unavailable choices with another product without the user’s direction.

Limits, retries and privacy

Keys share an account limit of 120 requests per minute, 10 upload-batch requests per hour and 5 video requests per 10 minutes. Respect Retry-After. JPEG, PNG and WebP files must be at most 4,000,000 bytes, 12,000px and 32 megapixels; the whole multipart request is limited to 4,200,000 bytes. JSON requests are limited to 16 KiB. Selected AI shots also need the original-photo requirements returned by capabilities.

Exact retry identities protect upload receipts, debit and render admission. If a request has an uncertain outcome, retry the same UUID and identical input; do not create another identity to force another render. A 402 means the existing balance is insufficient. Purchases stay in ReeltyPro’s normal billing flow.

An integration receives the photos and project information you authorize it to handle. Review its privacy policy. Photo storage, capacity, retention, payment reversals and review rules remain those of the existing product. Revoking a key blocks new requests; it does not cancel a job already admitted or revoke an already-issued short-lived media URL.

Privacy · Terms · Integration support