Platform guide
iOS integrations
SwiftHTTPJavaScript
Integrate Beladed into native iOS applications with Swift and a trusted backend.
Recommended architecture
App or site→Your trusted backend→Beladed API
Credentials
| Credential | Where it belongs | Use |
|---|---|---|
| No key | Any client | Explicitly public reads and redirect destinations |
| Publishable key | Approved web origin or extension | Narrow browser-safe operations; never grants administrative access |
| Secret key | Your trusted server only | Account-scoped reads and mutations |
| OAuth client | Backend authorization flow | Approved partner integrations |
Implementation checklist
- Choose a documented operation and verify platform support.
- Keep secret keys on your trusted backend.
- Restrict publishable keys to explicit origins and minimum permissions.
- Use HTTPS and validate every redirect or deep link.
- Handle offline, retry, duplicate, and expired-session states.
- Verify the development workflow before production.
Examples
Every operation reference provides language-specific HTTP examples. Client-platform examples use a backend relay unless the operation explicitly permits an origin-restricted publishable key.