Endpoint Reference
Customer API requests target https://api.sweetpotato.dev. The upstream manifest at commit
15236f98 contains 551 method/path entries. This source inventory groups the principal consumer
surfaces; it does not prove that every route is deployed.
| Method | Representative route | Purpose |
|---|---|---|
| GET | /api/auth/methods | Discover the application’s available auth methods |
| GET | /api/sessions/ | Read the authorized user’s session lifecycle |
| GET | /api/entitlements | Read application-authorized entitlements |
| GET | /api/stripe/products | Read products visible to the application |
| GET | /api/secure-messages | Read authenticated secure messages |
| GET | /api/v1/issue-reports | Read the authorized user’s issue reports |
| GET | /api/webhooks | Read application webhook configuration |
| GET | /api/dayrate/availability | Read dayrate availability |
These are representative routes, not a complete OpenAPI listing. Availability depends on application credentials, key type, user session, capability, and subscription. A route name alone does not grant access.
Request Example
curl --fail-with-body \
-H "X-API-Key: $SPAPS_API_KEY" \
--get --data-urlencode "user_id=<user-uuid>" \
--data-urlencode "entitlement_key=<feature-key>" \
https://api.sweetpotato.dev/api/entitlements/checkReplace the placeholders with an existing user UUID and feature key. This example uses a server-held secret key. For a browser’s own-user check, use a publishable key, allowed origin, and current user token. See Billing and entitlements.
Use the SDK/client methods when available so request and response contracts remain typed. SPAPS is pre-1.0; client packages have independent version numbers. Verify the installed client version and deployed API before relying on a newly documented endpoint.