Glossary
| Term | Meaning |
|---|---|
| Application | A SPAPS client boundary with credentials, allowed origins, settings, and access rules |
| Staging application | A hosted application used to integrate and test without production credentials or data |
| Production application | A separately provisioned hosted application for live traffic |
| Publishable key | Browser-facing key, typically spaps_pub_*, constrained by endpoint scope and origin |
| Secret key | Server-only key, typically spaps_sec_* or spaps_*, for privileged application calls |
| User session | Current signed user session; application access is checked separately |
| Entitlement | An access grant for a user or resource, evaluated by key and scope |
| Allowed origin | Exact browser origin permitted to use a publishable key |
| Downstream application | A customer application that calls the hosted SPAPS API |
Package Names
| Name | Purpose |
|---|---|
spaps-sdk | TypeScript client for browser and server integrations |
spaps / spaps_client | Python distribution and import path |
spaps-types | Shared TypeScript contracts |
spaps-wallet-utils | Wallet helpers in source; no verified public npm release |
spaps-issue-reporting-react | React issue-reporting components |