Start Here
SPAPS is hosted by Sweet Potato. You operate your application; you do not install or operate the SPAPS backend.
Customer Path
Request access and prepare the account
Request access at sweetpotato.dev/start/ . An operator prepares your account, the portal application’s server-side secret, the confirmed checkout price, and HTTPS return URLs. Sending the request does not create an account or activate a subscription.
Sign in, subscribe, and provision staging
In that prepared environment, sign in and subscribe. The current offer is $99 per month, with no free tier or trial. An active subscription permits up to three staging applications.
Record credentials safely
Save the one-time secret key in server-side secret storage. Use a publishable key in browser code.
Register every browser origin, including a precise localhost origin used during development.
Choose a client
- TypeScript:
npm install spaps-sdk - Python:
pip install spaps - Direct HTTP: use
https://api.sweetpotato.dev
Prove the staging path
Verify sign-in, session refresh, one representative API call, and an entitlement decision using the staging application. Keep payment, email, and webhook side effects scoped to the staging contract.
Promote configuration
Provision production credentials separately. Promote by replacing environment configuration, without changing the API integration or copying staging secrets.
Never place a secret key in browser code, a public environment variable, a repository, or client logs. Use a publishable key for browser calls and a secret key only from your server.