ข้ามไปยังเนื้อหา
การนำทางเอกสาร

เริ่มที่นี่

ผลิตภัณฑ์

การเชื่อมต่อ

SDK

MCP

SDK overview

Choose an integration

Add in-app feedback with the Swift SDK, or build a client against the SDK HTTP API. RevenueCat is optional; Upweight does not require it.

Publishable keys

As the workspace owner, select an app in SDK setup and create a publishable key. Keys start with upw_pk_. The full key is shown once; copy it before leaving. Only its hash and prefix are stored. The key selects your workspace and app and is public in the app binary. Never ship RevenueCat secret credentials in your app.

Release a new app version with a rotated key. Two active keys can overlap for the same app; creating a third retires the oldest. Revoke the previous key only when old app versions can stop using it. Revocation breaks requests from binaries still using that key.

Identify customers

Use your host app’s stable user ID. Use the same RevenueCat appUserID only when RevenueCat is connected. Changing the ID does not merge server identities. SDK email is write-only and unverified; it does not match RevenueCat customers or prove who the user is.

Observe a connection

Make a successful request from your app to record installation evidence. Recent-request evidence is sampled about every 60 seconds; the first successful request is recorded separately and survives key rotation or revocation. This is neither a live health check nor an identity proof.

If a request fails, check the selected app, key, stable ID and the API errors. Respect the retry delay on rate-limit responses.

Security boundaries

The key authorises workspace access, not a verified person. Someone who knows another customer’s app user ID could impersonate it, including their revenue attribution. Do not assume every malicious vote is unweighted. SDK responses expose plain vote counts, never revenue, subscription or classification data.

See Security and privacy, public board settings, and shipped-update emails for related boundaries.

ตรวจสอบล่าสุด