1. Install the released package
Add pod 'RapidoReach', '1.0.9' to your Podfile target, run pod install and open the generated .xcworkspace. Import RapidoReach in Swift.
Package and source referencePresent optional rewarded surveys from your iOS app with the RapidoReach CocoaPod and a server-verified currency flow.
RapidoReach CocoaPod 1.0.9 · Guide reviewed October 15, 2026
Public web playground · Sample inventory · Native presentation variesAdd the survey entry point to a visible UIKit screen or present it through your SwiftUI hosting controller. Configure privacy requirements before using advertising identifiers.
Add pod 'RapidoReach', '1.0.9' to your Podfile target, run pod install and open the generated .xcworkspace. Import RapidoReach in Swift.
Package and source referenceThe SDK requires iOS 12.0 or later. Review privacy disclosures and request ATT permission before using IDFA when required by your app’s data use.
Create a publisher app in the dashboard and use its SDK token with a stable, non-personal app user ID. The web UID signing App Key stays on your backend.
iOS integration referenceReplace the placeholders in your own app. Catch SDK errors in the calling screen, handle unavailable inventory and refresh balances from your server.
import UIKit
import RapidoReach
// Configure once after you know the signed-in user.
func initializeRewards() {
RapidoReach.shared.configure(
apiKey: "YOUR_API_TOKEN", user: "YOUR_USER_ID"
)
RapidoReach.shared.fetchAppUserID()
}
// Call from your visible UIViewController after readiness.
func openRewards(from controller: UIViewController) {
RapidoReach.shared.presentOfferwall(
from: controller, title: "Earn Rewards"
)
}These are screenshots of the public web playground, captured October 15, 2026. They show sample survey cards shared as a visual reference, not screenshots of a iOS native build or a guarantee of inventory.

This local interaction illustrates presentation states. It does not call the SDK, load live surveys or issue rewards.
A survey is available in this simulated placement.
Open the public widget playground ↗
The playground previews layout and themes. To validate iOS SDK behavior, use the package example and your own development app on a supported device.
Get the iOS package / exampleUse a development publisher app. In the app’s Test users section, add the raw app user ID exactly as your SDK sends it and enable Test mode for that test user. For web, generate the signed UID from that same raw user ID.
The test survey helps verify the journey. Keep test activity separate from live earnings.
Open the integration testing guideConfigure the app’s server callback and send a Test Callback from the dashboard. Verify the documented hash, attribute the transaction to the correct user and store it once. Repeat the same transaction to check duplicate handling.
Client reward notifications should refresh UI. They should not create a second credit.
Callback verification referenceInstall pods for the correct target and open the generated workspace. The public pod and import are RapidoReach.
Use a visible view controller, wait for registration and availability, and present on the main thread. Avoid presenting over another transition.
Use the SDK delegates for UI refresh and inspect your verified server callback. Closing a view is not proof of survey completion.
Trace the same app user ID and transaction through your callback receiver and reward ledger. Check hash verification, duplicate detection and currency conversion. Use redacted diagnostics when contacting support.
Create a publisher account, register your app and connect the first test user. Review the reward flow before opening the placement to live users.