Skip to main content
Offline Protocol has two SDK families. The Mesh SDK (v0.31.0) handles local device coordination on React Native, Python, Java, C, Ruby and Rust, including a constrained leaf for firmware, with preview Swift, Android and Flutter packages and an experimental browser binding. The OfflineID SDK (React 0.2.0, React Native 0.3.3) adds hosted account sign-in. Pick the row that matches what you are building. The Mesh SDK’s device identity is generated locally. The OfflineID SDK connects your application to the hosted OfflineID service. Choose one or both according to the workflow; neither is a prerequisite for the other. Pass the public App ID as appId in React 0.2.0 and React Native 0.3.3. Do not put a secret backend API key in the provider.

​
Allowed web origins

Add development and production origins in the portal’s Domains tab. Each entry must use HTTP or HTTPS and is stored as scheme://host[:port]; paths are dropped. Changes apply within about a minute. The gateway enforces the list for browser requests identifying an application with x-app-id or the older x-project-id. Once at least one origin is configured, an unlisted origin receives 403 with: “This origin is not allowed for this application. Add it under Domains in the developer portal.”
Origin checks are being rolled out. The gateway is temporarily in log-only mode; rejection starts when blocking is enabled.
Requests without an Origin header, including native applications, servers and the CLI, are not checked. Applications with no configured origins are also not checked. This is not a security boundary for non-browser callers.