Skip to content
Hardcount
Run it locally
Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

Switch the dashboard session between test and live mode

POST
/v1/auth/mode
curl --request POST \
--url http://localhost:8080/v1/auth/mode \
--header 'Content-Type: application/json' \
--cookie hardcount_session=<hardcount_session> \
--data '{ "livemode": true }'

Updates dashboard_sessions.livemode for the cookie session. All subsequent requests inherit the new mode via session middleware, so customers / invoices / subscriptions / API keys reads filter to the active mode without per-call mode parameters. The same operator flips back and forth without re-authenticating.

Media typeapplication/json
object
livemode
required
boolean

Example generated

{
"livemode": true
}

Mode updated

Media typeapplication/json
object
livemode
required
boolean

Example generated

{
"livemode": true
}

Missing or expired session

Media typeapplication/json
object
error
object
type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string
code
string
message
string
request_id
string
param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
"error": {
"type": "invalid_request_error"
}
}