Our recommendation: prioritise existing integrations before expanding the catalogue. Start with the signing deadline below, then check that your launch monitoring measures a playable game and your permission records cover the intended use.
1. Does your Slots Launch integration need migrating?
Slots Launch’s current documentation names 15 November 2026 as its signed-request migration date. It says iframe embeds and API calls require server-side signing, with unsigned requests rejected after the deadline unless account-level legacy mode is enabled. The API secret belongs on the server, not in browser JavaScript. This is a documented forthcoming requirement, not an outage observed by this desk. (docs.slotslaunch.com)
Action for engineering: inventory token-only embeds and catalogue jobs, confirm the account’s cutover arrangements with support, and test the applicable plugin or backend implementation before deployment. Do not assume legacy access will be granted.
Check caching separately. The direct-embed guide warns against storing signed URLs in full-page HTML caches beyond their expiry. Test a cached page after the original signature expires—not only immediately after publishing it. (docs.slotslaunch.com)
2. Which releases should editors prepare for?
Pragmatic Play’s live catalogue lists Sweet Loot for 29 October and Killer Night for 2 November 2026. It also presents a play link for Chests Of Cai Shen – Infinity. These are studio catalogue signals; this desk has not established independent US-facing embedding permission or tested territorial availability for these titles. (pragmaticplay.com)
Action for content: create separate fields for announced release, editorial readiness, permission status and tested availability. A forthcoming release can enter the sourcing backlog without being advertised as playable on your website.
3. Does “iframe loaded” mean the slot is playable?
No. An iframe’s load event is not a reliable game-ready signal. MDN documents that the event can fire even when iframe content fails to load. A green wrapper-page check therefore cannot establish that a visitor reached playable controls. (developer.mozilla.org)
For a slot demo iframe not loading on mobile Safari, include storage behaviour in the investigation: WebKit documents default third-party cookie blocking under Intelligent Tracking Prevention. That is a diagnostic consideration, not proof of the cause of any particular failure. (webkit.org)
Action for product and engineering: record launch attempt, observed readiness or timeout, browser, device, network and consent state. Keep “readiness not observable” distinct from both success and failure.
4. Can a public demo URL serve as permission evidence?
Our procurement answer is no: record permission separately from accessibility. The US Copyright Office distinguishes licensed or permitted uses from uses relying on statutory exceptions or public-domain status. Finding material online does not identify which basis applies to your proposed use. (copyright.gov)
Action for the budget owner: request a written schedule covering the named domains, intended audience, embedding method, promotional placement, assets and duration. Ask the distributor to explain its authority to grant those rights. This is a purchasing safeguard, not a blanket legal conclusion about every form of linking.
5. Are commercial disclosures close enough to the recommendation?
Review the page around the demo, not just the game frame. FTC guidance says affiliate relationships should be disclosed clearly and conspicuously, close to the recommendation. It also warns that readers may not understand the label “affiliate link” by itself. (ftc.gov)
Action for editorial: inspect the mobile presentation of reviews and referral buttons. Use plain language explaining the commercial relationship rather than relying on a footer or an unexplained label.