An integration is useful when it removes a real handoff. For a brokerage or property-management team, that might mean bringing a QwikVid order into the same system that already holds the property record, then making the correct delivered media available to the right people.
Start by identifying one repetitive task: checking whether media is ready, finding the current download, or copying a link into a property record. A narrow first workflow is easier to verify than trying to automate every step of booking and delivery at once.
Give the property and order a reliable connection
Your system may identify a property with an internal ID, while QwikVid identifies an order with a numeric order number and a separate ticket ID. Keep that relationship explicitly. Street addresses alone are fragile identifiers: formatting changes, units matter, and one property can have more than one shoot.
For example, your property record might hold your internal property ID, the QwikVid order number for support conversations, and the ticket ID used to request details. A repeat shoot should be a separate order relationship, not an overwrite of the earlier delivery history.
Read status, then check the specific media
The order list lets an authorized integration find existing orders. The order-detail response provides more specific delivery information. Use these together to answer two separate questions: what is happening with the order, and is the particular file your user needs available?
- Retrieve orders visible to the integration's QwikVid user.
- Store the ticket ID against the correct property record.
- Read that order's details when the workflow needs an update.
- Check download eligibility and the relevant package or media field.
- Present the intended link, labelled with the type of media it opens.
Photos, a listing video and a 3D tour are separate deliverables. Avoid a single “everything is ready” flag based only on one nonempty URL. High-resolution photos also have their own entitlement and readiness; they should not be assumed to be included with every order.
Preserve the difference between media versions
Keep standard and high-resolution photo packages distinct. Keep branded and MLS video links distinct. This gives a team member a meaningful choice and avoids publishing the wrong version to a destination with different requirements.
Use returned URLs as supplied, rather than constructing storage paths from a ticket ID or assuming a particular filename. Before displaying a download, enforce the user's account access and check the current delivery response. Plan for a file that is temporarily unavailable, and give the user a clear way to refresh or contact support.
Build an honest failure state
A successful network connection does not always mean the request succeeded. QwikVid's existing read endpoints have different response shapes, and the order-detail endpoint can return an error object with HTTP 200. Check the documented JSON result as well as the HTTP status.
If a background refresh fails, keep the last known result with its last-checked time. Do not replace it with an empty list that looks like all orders disappeared. Retry temporary read failures a limited number of times, but stop and investigate invalid credentials or denied access.
Agree the operating rules before expanding
Discuss the accounts involved, the expected number of orders, the update frequency and who handles exceptions. Keep API keys on your server and out of public pages. Arrange approved test access before pointing an automated workflow at production.
Ordering, scheduling changes and status notifications require more than a read request. Before automating them, agree the supported contract, how duplicate requests are handled, when a booking is confirmed, and what happens if the connection fails partway through. The current public quickstart focuses on reading existing orders; it does not promise a public webhook subscription or self-service booking API.
Start with a working read integration
The QwikVid Developer Center includes a quickstart, endpoint reference and downloadable Postman collection with blank credential variables. Use it to connect one approved account and confirm that order IDs, media readiness and error handling behave as your team expects.
Once that handoff is reliable, bring us the next workflow you want to automate. A clear property-to-order-to-media path gives both teams a concrete starting point.
Need help with a QwikVid order? Visit the Help Center or contact the team with the order number and what you need to resolve.