# Atmosplay > Atmosplay was a mobile advertising technology company, founded in 2014 in Budapest, Hungary, that built interactive 3D "playable" ads and an ad-monetization platform for mobile game publishers. Its ATMIQ cloud gameplay engine let a user try a game inside an ad without installing it, and its self-serve builder produced playable creatives for 3D and action games. Speedinvest led its Series A in 2016; the company was acquired by ZPLAY Information Technology on 2018-01-01. > STATUS: END OF LIFE. Atmosplay is not a live provider. Its domains are gone — atmosplay.com serves a HugeDomains "for sale" parking page on every path and every subdomain, and atmosplay.net does not resolve. The only surviving first-party surface is the GitHub organization github.com/Atmosplay, whose ten repositories were last pushed between 2019-12 and 2020-06. Do not attempt to call an Atmosplay endpoint; do not treat the parked domain's HTTP 200 responses as evidence of a live service. > NO PUBLIC API. Atmosplay published no OpenAPI, AsyncAPI, GraphQL SDL, MCP server, or A2A agent card. Contract discovery was run against atmosplay.com and eight subdomains (api., ads., sdk., docs., dev., developer., platform., console.) at /openapi.json, /swagger.json and every relevant /.well-known/ path; all returned the same parking-page HTML. The integration surface was, and remains, client SDKs. > A REST "Report API" DID exist for publishers, but its reference and credentials both lived inside the Atmosplay dashboard, which is offline. Its base URL, endpoints, and auth model are not recoverable from any public source and are not reconstructed anywhere in this profile. ## Products - [AtmosplayAds SDK](https://github.com/Atmosplay/AtmosplayAds-Android): Mobile ad SDK for Android, iOS and Unity. Ad formats: banner, interstitial, rewarded video, native (managed rendering and self rendering), splash, float ad, window ad. - [Mediation adapters](https://github.com/Atmosplay): First-party adapters for Google AdMob and MoPub, so publishers could take Atmosplay demand through an existing mediation stack. MoPub itself was shut down in 2021. ## Documentation - [Publisher Help Center](https://github.com/Atmosplay/Help-Center-for-Publisher): Dashboard guide — apps, ad units, reporting, financial management. English and Chinese. - [Android integration guide (English wiki)](https://github.com/Atmosplay/AtmosplayAds-Android/wiki): Get started, import the SDK, per-format integration, GDPR, debugging. - [iOS integration guide](https://github.com/Atmosplay/AtmosplayAds-iOS): CocoaPods and manual install, per-format integration, GDPR, test IDs. - [Unity integration guide](https://github.com/Atmosplay/AtmosplayAds-Unity): Unity plugin, package import, C# callback handlers. - [Debugging: test IDs and error codes](https://github.com/Atmosplay/AtmosplayAds-Android/wiki/Debugging): The published test identifiers and the 11-code error table. ## Packages - CocoaPods `AtmosplayAds` — 3.2.1, published 2020-06-03. The only Atmosplay package still installable from a live registry. - Gradle `com.atmosplayads:atmosplayads:3.1.0` — was hosted on JCenter/Bintray, sunset in 2021, never migrated to Maven Central. The dependency line printed in Atmosplay's own README no longer resolves. - Unity `.unitypackage` — 3.2.1, attached to a GitHub release on 2020-06-05. ## Credentials - APP_ID and AD_UNIT_ID, both uppercase UUIDs, issued by the (now offline) publisher dashboard and passed to the SDK in application code. Identifiers, not secrets. - Atmosplay published fixed public TEST APP_ID/AD_UNIT_ID pairs per ad format per platform, which returned house creatives and generated no revenue. They are recorded verbatim in this profile's sandbox artifact. - No OAuth 2.0, no OpenID Connect, no scopes. ## Compliance - GDPR: a three-state publisher-supplied consent API since SDK 2.6.0 (PERSONALIZED / NON_PERSONALIZED / UNKNOWN) on both Android and iOS. - MSA Alliance OAID: the Android guide instructs publishers to bundle the MSA SDK so an OAID can be read on Android 10+ in mainland China. - No IAB TCF, no CCPA signalling, no COPPA flag, no OpenRTB, and no published certification of any kind (no SOC 2, ISO 27001, PCI DSS, HIPAA or FedRAMP). No trust center, no security.txt, no vulnerability disclosure program. ## Successor - [ZPLAY Ads](https://github.com/zplayads): The acquirer. ZPLAY publishes its OWN publisher Report API reference against pa-report.zplayads.com / pa-report-en.zplayads.com, plus an H5 playable-creative specification and its own help centers. Those documents describe ZPLAY's hosts, dashboard and account model — they are ZPLAY's contract, not Atmosplay's, and this profile deliberately does not adopt them. Anyone looking for a live playable-ads API from this lineage should look at ZPLAY Ads, not Atmosplay. ## Notes - Generated by the API Evangelist enrichment pipeline from Atmosplay's own surviving public surface. Nothing here is fabricated; where a value could not be established it is recorded as absent rather than guessed. - This is an independent third-party profile. API Evangelist does not operate or represent Atmosplay.