DEVELOPER ACCESS / CURRENT AVAILABILITY

Start with
authorized access.

SPAPS access currently requires operator setup. The developer plan is $99/month for up to three staging applications, with no free tier and no trial.

OPERATOR SETUPPRE-1.0

Before you subscribe

Request developer access at hello@sweetpotato.dev. An operator must prepare your account and trusted CLI environment before you subscribe.

If you already work with SPAPS, use your existing operator contact to arrange setup.

Public self-service signup is not available here. Email requests do not create an account or activate a subscription.

Request access by email Already have access? Continue These instructions do not create an account or grant API access.

What your operator prepares

An existing account

An authorized SPAPS account and a supported sign-in method. The portal login command signs in; it does not register a new customer.

A trusted CLI environment

An approved CLI installation and the portal application's server-side secret configured as SPAPS_API_KEY. That secret stays in the authorized terminal or server, never in a browser.

The developer subscription

The confirmed Stripe price and its mapping to dev-portal:active. Your operator must confirm that the hosted checkout is ready before you pay.

Working return pages

Actual HTTPS success and cancel URLs whose origins the portal application allows. Both pages must be reachable; the CLI's default API-host paths are not a substitute.

AFTER OPERATOR SETUP

Sign in.
Then activate access.

1. Sign in with your existing account

Run these commands in the prepared environment. Enter your password at the prompt. If your account requires MFA, ask your operator for a supported sign-in session; portal login cannot complete an MFA challenge.

export SPAPS_API_URL=https://api.sweetpotato.dev
spaps portal login
spaps portal status

2. Activate the developer subscription

If status already reports an active entitlement, continue to application creation. Otherwise, have your operator set the confirmed price ID and both return URLs below, then run:

spaps portal subscribe \
  --price-id "${SPAPS_DEV_PORTAL_PRICE_ID:?}" \
  --success-url "${SPAPS_CHECKOUT_SUCCESS_URL:?}" \
  --cancel-url "${SPAPS_CHECKOUT_CANCEL_URL:?}"

Complete the returned Stripe checkout in your browser, then check spaps portal status for active access. A redirect alone does not confirm activation. If payment completed but access is pending, use spaps portal subscribe --poll-only and follow up with your operator.

3. Create a staging application

spaps portal mint my-staging-app

After activation, this creates an application within your quota and shows its secret once. Store it immediately in your application's secret manager. It is separate from the portal credential used above.

Use your application's scoped credentials with the hosted API. Publishable keys belong in browser flows; secret keys stay on trusted servers.

Continue with the integration docs →

Start withauthorized access.