Stripe: Retrieve an Account Capability
Stripe accounts.getAccountsAccountCapabilitiesCapability: arguments, response, policy and SDK examples.
← Accounts operations · Get started
Operation stripe.getaccountsaccountcapabilitiescapability
Provider route: GET /v1/accounts/{account}/capabilities/{capability}. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/stripe with npm, or alter-sdk-stripe with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { StripeIntegration } from "@alter-ai/stripe";
async function execute(input: Parameters<StripeIntegration["accounts"]["getAccountsAccountCapabilitiesCapability"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new StripeIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.accounts.getAccountsAccountCapabilitiesCapability(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_stripe import StripeIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = StripeIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.accounts.get_accounts_account_capabilities_capability(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.account | string | Required within parent | Maximum length: 5000 |
path.capability | string | Required within parent | |
query | object | Optional | Additional keys: not allowed |
query.expand | array | Optional | |
query.expand[] | string | Each item | Maximum length: 5000 |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Update an Account Capability — response body |
Referenced models: Update an Account Capability — response body
Schemas
Section titled “Schemas”708 more schemas are linked from the tables above, on the schema pages.
Update an Account Capability — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | This is an object representing a capability for a Stripe account. Related guide: [Account capabilities](https://docs.stripe.com/connect/account-capabilities) |
account | JSON | Required within parent | The account for which the capability enables functionality. |
account (anyOf 1) | string | Alternative | Maximum length: 5000 |
account (anyOf 2) | Model | Alternative | Expand Create an account — response body |
future_requirements | Model | Optional | Expand Update an Account Capability — response body — future requirements |
id | string | Required within parent | The identifier for the capability. Maximum length: 5000 |
object | string | Required within parent | String representing the object's type. Objects of the same type share the same value. Known values: capability |
requested | boolean | Required within parent | Whether the capability has been requested. |
requested_at | JSON | Optional | |
requested_at (anyOf 1) | JSON | Alternative | |
requested_at (anyOf 1) (anyOf 1) | integer | Alternative | Time at which the capability was requested. Measured in seconds since the Unix epoch. Format: unix-time |
requested_at (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
requested_at (anyOf 2) | null | Alternative | |
requirements | Model | Optional | Expand Update an Account Capability — response body — requirements |
status | string | Required within parent | The status of the capability. Known values: active, inactive, pending, unrequested |
Referenced models: Create an account — response body, Update an Account Capability — response body — future requirements, Update an Account Capability — response body — requirements
Update an Account Capability — response body — future requirements
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
alternatives | JSON | Optional | |
alternatives (anyOf 1) | array | Alternative | Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields. |
alternatives (anyOf 1)[] | Model | Each item | Expand Create an account — response body — requirements alternatives array item |
alternatives (anyOf 2) | null | Alternative | |
current_deadline | JSON | Optional | |
current_deadline (anyOf 1) | JSON | Alternative | |
current_deadline (anyOf 1) (anyOf 1) | integer | Alternative | Date on which `future_requirements` becomes the main `requirements` hash and `future_requirements` becomes empty. After the transition, `currently_due` requirements may immediately become `past_due`, but the account may also be given a grace period depending on the capability's enablement state prior to transitioning. Format: unix-time |
current_deadline (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
current_deadline (anyOf 2) | null | Alternative | |
currently_due | array | Required within parent | Fields that need to be resolved to keep the capability enabled. If not resolved by `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash. |
currently_due[] | string | Each item | Maximum length: 5000 |
disabled_reason | JSON | Optional | |
disabled_reason (anyOf 1) | string | Alternative | This is typed as an enum for consistency with `requirements.disabled_reason`, but it safe to assume `future_requirements.disabled_reason` is null because fields in `future_requirements` will never disable the account. Known values: other, paused.inactivity, pending.onboarding, pending.review, platform_disabled, platform_paused, rejected.inactivity, rejected.other, rejected.unsupported_business, requirements.fields_needed |
disabled_reason (anyOf 2) | null | Alternative | |
errors | array | Required within parent | Fields that are `currently_due` and need to be collected again because validation or verification failed. |
errors[] | Model | Each item | Expand Update an Account Capability — response body — requirements errors item |
eventually_due | array | Required within parent | Fields you must collect when all thresholds are reached. As they become required, they appear in `currently_due` as well. |
eventually_due[] | string | Each item | Maximum length: 5000 |
past_due | array | Required within parent | Fields that haven't been resolved by `requirements.current_deadline`. These fields need to be resolved to enable the capability on the account. `future_requirements.past_due` is a subset of `requirements.past_due`. |
past_due[] | string | Each item | Maximum length: 5000 |
pending_verification | array | Required within parent | Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending. |
pending_verification[] | string | Each item | Maximum length: 5000 |
Referenced models: Create an account — response body — requirements alternatives array item, Update an Account Capability — response body — requirements errors item
Update an Account Capability — response body — requirements
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
alternatives | JSON | Optional | |
alternatives (anyOf 1) | array | Alternative | Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields. |
alternatives (anyOf 1)[] | Model | Each item | Expand Create an account — response body — requirements alternatives array item |
alternatives (anyOf 2) | null | Alternative | |
current_deadline | JSON | Optional | |
current_deadline (anyOf 1) | JSON | Alternative | |
current_deadline (anyOf 1) (anyOf 1) | integer | Alternative | The date by which all required account information must be both submitted and verified. This includes fields listed in `currently_due` as well as those in `pending_verification`. If any required information is missing or unverified by this date, the account may be disabled. Note that `current_deadline` may change if additional `currently_due` requirements are requested. Format: unix-time |
current_deadline (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
current_deadline (anyOf 2) | null | Alternative | |
currently_due | array | Required within parent | Fields that need to be resolved to keep the capability enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the capability is disabled. |
currently_due[] | string | Each item | Maximum length: 5000 |
disabled_reason | JSON | Optional | |
disabled_reason (anyOf 1) | string | Alternative | Description of why the capability is disabled. [Learn more about handling verification issues](https://docs.stripe.com/connect/handling-api-verification). Known values: other, paused.inactivity, pending.onboarding, pending.review, platform_disabled, platform_paused, rejected.inactivity, rejected.other, rejected.unsupported_business, requirements.fields_needed |
disabled_reason (anyOf 2) | null | Alternative | |
errors | array | Required within parent | Fields that are `currently_due` and need to be collected again because validation or verification failed. |
errors[] | Model | Each item | Expand Update an Account Capability — response body — requirements errors item |
eventually_due | array | Required within parent | Fields you must collect when all thresholds are reached. As they become required, they appear in `currently_due` as well, and `current_deadline` becomes set. |
eventually_due[] | string | Each item | Maximum length: 5000 |
past_due | array | Required within parent | Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the capability on the account. |
past_due[] | string | Each item | Maximum length: 5000 |
pending_verification | array | Required within parent | Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending. |
pending_verification[] | string | Each item | Maximum length: 5000 |
Referenced models: Create an account — response body — requirements alternatives array item, Update an Account Capability — response body — requirements errors item
Create an account — response body — groups The groups associated with the account payments pricing
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
payments_pricing | JSON | Optional | |
payments_pricing (anyOf 1) | string | Alternative | The group the account is in to determine their payments pricing, and null if the account is on customized pricing. [See the Platform pricing tool documentation](https://docs.stripe.com/connect/platform-pricing-tools) for details. Maximum length: 5000 |
payments_pricing (anyOf 2) | null | Alternative |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: stripe.getaccountsaccountcapabilitiescapability. Catalog operation: GetAccountsAccountCapabilitiesCapability. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Pinned headers: {"Stripe-Version": "2026-09-30.endive"}