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 →

List Stripe connections

GET
/v1/settings/stripe
curl --request GET \
--url http://localhost:8080/v1/settings/stripe \
--header 'Authorization: Bearer <token>'

Returns the tenant’s Stripe connections for both modes in one list (at most two rows, live first), whatever the caller’s mode. No secret values are returned, only prefixes and last four characters.

Connections

Media typeapplication/json
object
data
required
Array<object>
<= 2 items
object
id
required

Also the {id} in the Stripe webhook URL /v1/webhooks/stripe/{id}.

string
tenant_id
required
string
livemode
required
boolean
stripe_account_id

Set after Stripe accepted the key.

string
stripe_account_name
string
secret_key_prefix

First 12 characters of the secret key.

string
secret_key_last4
required
string
publishable_key
required
string
webhook_secret_last4
string
has_webhook_secret
required
boolean
verified_at

Last time Stripe accepted the key.

string format: date-time
last_verified_error

Why the last Stripe check failed, in Stripe’s own words (or the network error when Stripe was not reached). Empty when it passed.

string
last_verified_error_kind

What kind of failure last_verified_error is. rejected: Stripe answered and refused the key (invalid, revoked, or without access). unavailable: Stripe was not reached, or answered 429/5xx, so the key was not checked; connecting again may work. Absent when the check passed, and on keys that failed before this field existed.

string
Allowed values: rejected unavailable
created_at
required
string format: date-time
updated_at
required
string format: date-time
retries_queued

Connect response only. Number of stuck invoices being retried in the background.

integer

Example

{
"data": [
{
"last_verified_error_kind": "rejected"
}
]
}