GET/apps/accounting/v1/stripe-connect

The workspace's Stripe Connect status and Vision's fee. With `confirm`, first finishes a Connect started by this same signed-in person.

The approved contract does not provide a longer purpose statement for this operation.

App
Accounting
Contract
Accounting API 0.32.0
Lifecycle
preview
Runtime
not-public
Operation ID
getStripeConnectStatus
Canonical origin
https://accounting.runonvision.com

Purpose and use cases

The workspace's Stripe Connect status and Vision's fee. With `confirm`, first finishes a Connect started by this same signed-in person.

The owning App is Vision Accounting. Accounting owns financial records, exact arithmetic, approvals, audit evidence, workspace grants, and ledger invariants.

Business use cases and out-of-scope behavior are not yet declared in the approved OpenAPI description.

Request

GET https://accounting.runonvision.com/apps/accounting/v1/stripe-connect

Authentication and authorization

Send a Vision-issued bearer token for the exact App audience. The token must include the accounting entitlement and satisfy the aws-… accounting workspace required binding.

  • Required scope: accounting:providers:read

Human roles are not declared in OpenAPI. Record-level and business permission checks remain the owning App's authority.

Headers

  • Authorization: Bearer <access-token> — required.
  • Accept: application/json — recommended where a JSON response is declared.

Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.

Path and query parameters

NameLocationTypeRulesDescription
confirmquerystringoptional; pattern ^AWS-[A-Z0-9]{12}\.[A-Za-z0-9_-]{43}$The confirmation token Stripe's return put on Settings › Online payments. Links the account only when the caller is the person who pressed Connect; anyone else burns it and nothing is linked.

Request body

This operation declares no request body.

Runnable examples

cURL
curl 'https://accounting.runonvision.com/apps/accounting/v1/stripe-connect' \
  --request GET \
  --header 'authorization: Bearer ${ACCESS_TOKEN}' \
  --header 'accept: application/json'
JavaScript (server-side)
const response = await fetch('https://accounting.runonvision.com/apps/accounting/v1/stripe-connect', {
  method: 'GET',
  headers: {
    authorization: `Bearer ${ACCESS_TOKEN}`,
    accept: 'application/json',
  },
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()
Python 3 standard library
import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://accounting.runonvision.com/apps/accounting/v1/stripe-connect',
    data=None,
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer <ACCESS_TOKEN>"
},
    method='GET',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.

Responses

StatusMeaningSchema
200Statusobject
401Safe Accounting errorobject
403Safe Accounting errorobject
503Safe Accounting errorobject

Success response schema

FieldTypeRulesDescription
schemaVersion"vision-accounting-stripe-connect-status.v1"requiredNot described in the contract.
availablebooleanrequiredNot described in the contract.
modetest | liveoptionalNot described in the contract.
connectedbooleanrequiredNot described in the contract.
statusLabelstringrequiredOne plain sentence for people about the status. While `available` is false it reads "Online payments aren't turned on for your account yet."
accountReferencestring | nulloptional; pattern ^acct_[A-Za-z0-9]+$Not described in the contract.
accountNamestring | nulloptionalThe account's name, or its masked acct_ id (acct_…X7Q2) while Stripe has none. Null only when not connected.
finishSetupUrlstring | null · urioptionalWhere the account's owner finishes setting it up in Stripe; null once Stripe has what it needs.
countrystring | nulloptionalNot described in the contract.
defaultCurrencystring | nulloptionalNot described in the contract.
chargesEnabledbooleanoptionalNot described in the contract.
payoutsEnabledbooleanoptionalNot described in the contract.
detailsSubmittedbooleanoptionalNot described in the contract.
connectedAtstring | null · date-timeoptionalNot described in the contract.
legacyRestrictedKeybooleanoptionalA restricted key saved before Connect is on file. It cannot take payments; connect with Stripe to replace it.
feeDisplaystringoptionalNot described in the contract.
feeBasisPointsintegeroptional; minimum 0; maximum 10000Not described in the contract.
feeCapMinorUnitsstringoptional; pattern ^[0-9]+$Not described in the contract.
feeCurrencystringoptional; pattern ^[A-Z]{3}$Not described in the contract.
poweredByVisionbooleanoptionalNot described in the contract.
chargesLabelstringoptionalNot described in the contract.
payoutsLabelstringoptionalNot described in the contract.
poweredByVisionLabelstringoptionalNot described in the contract.
modeLabelstringoptionalNot described in the contract.
reasonstringoptionalOnly while `available` is false: why online payments are off. "online_payments_not_set_up" (no Stripe platform configured), "live_stripe_not_enabled" (a live key without live Stripe turned on) or "stripe_config_invalid" (a platform value is malformed).
200 illustrative response
{
  "schemaVersion": "vision-accounting-stripe-connect-status.v1",
  "available": true,
  "mode": "test",
  "connected": true,
  "statusLabel": "<statusLabel>",
  "accountReference": "<accountReference>",
  "accountName": "<accountName>",
  "finishSetupUrl": "<finishSetupUrl>",
  "country": "<country>",
  "defaultCurrency": "<defaultCurrency>",
  "chargesEnabled": true,
  "payoutsEnabled": true,
  "detailsSubmitted": true,
  "connectedAt": "2026-08-21T18:00:00Z",
  "legacyRestrictedKey": true,
  "feeDisplay": "<feeDisplay>",
  "feeBasisPoints": 0,
  "feeCapMinorUnits": "<feeCapMinorUnits>",
  "feeCurrency": "<feeCurrency>",
  "poweredByVision": true,
  "chargesLabel": "<chargesLabel>",
  "payoutsLabel": "<payoutsLabel>",
  "poweredByVisionLabel": "<poweredByVisionLabel>",
  "modeLabel": "<modeLabel>",
  "reason": "<reason>"
}

Errors and troubleshooting

Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.

  • 401 — Safe Accounting error
  • 403 — Safe Accounting error
  • 503 — Safe Accounting error

Collection behavior

Pagination: not declared. Filtering/search: not declared. Sorting: not declared.

Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.

Operational behavior

  • Rate limit: No operation-specific limit or 429 response is declared.
  • Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
  • Idempotency: No idempotency header or replay window is declared.
  • Concurrency: No ETag, If-Match, or optimistic-version header is declared.

Security and privacy

  • Keep client credentials and bearer tokens on trusted servers.
  • Send only to the exact approved HTTPS origin and audience.
  • Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
  • Do not log credentials, tokens, complete private payloads, or secrets.

Edge cases and known documentation gaps

  • No detailed operation description.
  • Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Contract history and evidence