Plan and test the signed-request migration before 15 November 2026. As of this research date, that deadline is in the future; Slots Launch’s documentation says unsigned iframe and API requests will be rejected after the transition unless account-level legacy mode is enabled. (docs.slotslaunch.com)
Its direct-embed documentation describes server-generated signed URLs, expiry values and registered-domain matching. It also says its lightweight WordPress embed plugin obtains signed URLs through AJAX to avoid serving expired signatures from full-page caches. (docs.slotslaunch.com)
Recommended migration checklist:
- Inventory all hard-coded embeds and API integrations across every domain.
- Confirm the account’s registered domains and credential ownership.
- Obtain the appropriate plugin or implement the documented backend signing flow.
- Test cache expiry, signature expiry and domain mismatches deliberately.
- Verify both catalogue synchronisation and visitor launches.
- Check staging and production independently.
- Ask support to confirm any legacy-mode exception in writing.
- Agree the exact cutover timing and rollback route with the supplier.
Do not use a preview link as a permanent production integration. The supplier also prohibits bypassing its iframe to extract the final game URL. (docs.slotslaunch.com)
This is a documented supplier requirement, not an observed outage or a claim that every customer account has identical migration settings.