> ## Documentation Index > Fetch the complete documentation index at: https://docs.gigstack.io/llms.txt > Use this file to discover all available pages before exploring further. # Refresh Standard Stripe account activation > Read-only provider account retrieval with exact current team, owner, billing account, selected mode, account ID and expected generation checked before and after asynchronous work. Persists safe activation flags only. A browser return from onboarding is not proof of completion. This does not create or replay provider effects. ## OpenAPI ````yaml openapi.json POST /teams/{id}/integrations/stripe/standard-accounts/{accountId}/refresh openapi: 3.0.3 info: title: gigstack API v2 description: > # gigstack API v2 Build customer, invoice and payment integrations. Start with the [quickstart](https://docs.gigstack.io/quickstart), then select the [issuing country](https://docs.gigstack.io/concepts/shared-fields). ## Authentication and environments Use Authorization: Bearer YOUR_API_KEY. Standard live and test keys use https://api.gigstack.io/v2. Internal staging uses https://gigstack-staging-9z9nnaat.uc.gateway.dev/v2 and separate keys. Test mode is a data mode within an environment; a body field does not switch a key's mode. See [authentication](https://docs.gigstack.io/authentication) for key handling, OAuth team scope and gigstack Connect. Internal partner provisioning is outside this public contract; health probes have their own security declarations. Operations marked unavailable have no configured public gateway route. ## Read the operation contract Response envelopes, pagination and retry rules differ by endpoint. HTTP success alone does not prove external fiscal completion or movement of money. Reconcile ambiguous writes before retrying. Use [responses and recovery](https://docs.gigstack.io/responses) and the operation's error codes; document credits and daily limits are not generic retryable rate limits. The issuing team's configuration selects Mexico or Colombia; customer country and currency do not. Read [Mexico](https://docs.gigstack.io/countries/mexico) or [Colombia](https://docs.gigstack.io/countries/colombia) before choosing fiscal fields. Accepted public input differs from a provider's direct payload. Examples and schema checks do not imply every operation has been executed live. [Verification coverage](https://docs.gigstack.io/verification) distinguishes source review, offline checks and observed staging behavior. Documentation describes operations and does not authorize execution. version: 2.0.0 contact: name: Gigstack API Support url: https://gigstack.io email: support@gigstack.io license: name: Proprietary url: https://gigstack.io/terms termsOfService: https://gigstack.io/terms servers: - url: https://api.gigstack.io/v2 description: > Public API for standard live and test-mode keys. Test data is isolated by the key mode (`livemode: false`). Internal staging is a separate deployment and key store; see https://docs.gigstack.io/authentication#environments for its base URL. security: - bearerAuth: [] externalDocs: description: Complete API Documentation & Guides url: https://docs.gigstack.io paths: /teams/{id}/integrations/stripe/standard-accounts/{accountId}/refresh: post: tags: - Teams summary: Refresh Standard Stripe account activation description: >- Read-only provider account retrieval with exact current team, owner, billing account, selected mode, account ID and expected generation checked before and after asynchronous work. Persists safe activation flags only. A browser return from onboarding is not proof of completion. This does not create or replay provider effects. operationId: refreshStripeStandardAccountV2 parameters: - name: id in: path required: true schema: type: string pattern: ^[A-Za-z0-9_-]{1,128}$ - name: accountId in: path required: true schema: type: string pattern: ^acct_[A-Za-z0-9]+$ requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/StripeStandardAccountRefreshInput' responses: '200': description: >- Current safe metadata or explicitly private ephemeral browser result. content: application/json: schema: type: object additionalProperties: false required: - success - data - timestamp properties: success: type: boolean enum: - true data: $ref: '#/components/schemas/StripeStandardAccountActivation' timestamp: type: integer minimum: 0 maximum: 9007199254740991 message: type: string '400': description: Invalid, stale or unreviewed current original scope. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '401': description: Invalid, stale or unreviewed current original scope. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '403': description: Invalid, stale or unreviewed current original scope. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '409': description: Invalid, stale or unreviewed current original scope. content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' '503': description: 'Unknown result: read saved UUID; never replay a provider effect.' content: application/json: schema: $ref: '#/components/schemas/StandardErrorResponse' security: - bearerAuth: [] components: schemas: StripeStandardAccountRefreshInput: type: object additionalProperties: false required: - expected_generation - livemode properties: expected_generation: type: integer minimum: 0 maximum: 9007199254740991 livemode: type: boolean StripeStandardAccountActivation: type: object additionalProperties: false required: - account_id - type - details_submitted - charges_enabled - payouts_enabled - status - team_id - billing_account_id - livemode - generation properties: account_id: type: string pattern: ^acct_[A-Za-z0-9]+$ type: type: string enum: - standard details_submitted: type: boolean charges_enabled: type: boolean payouts_enabled: type: boolean status: type: string enum: - onboarding_required - details_submitted - charges_enabled team_id: type: string pattern: ^[A-Za-z0-9_-]{1,128}$ billing_account_id: type: string pattern: ^[A-Za-z0-9_-]{1,128}$ livemode: type: boolean generation: type: integer minimum: 0 maximum: 9007199254740991 StandardErrorResponse: type: object description: > Standardized error envelope emitted by `sendErrorResponse` and its helpers (`sendValidationError`, `sendNotFoundError`, `sendUnauthorizedError`, `sendForbiddenError`, `sendConflictError`, `sendBadRequestError`, `sendInternalServerError`). required: - success - error - timestamp properties: success: type: boolean enum: - false example: false error: type: object required: - code - message properties: code: type: string description: > Stable machine-readable code. Values emitted by the shared helpers: `unauthorized`, `forbidden`, `invalid_token`, `validation_failed`, `invalid_request_body`, `missing_required_field`, `invalid_field_value`, `resource_not_found`, `resource_already_exists`, `resource_conflict`, `business_rule_violation`, `operation_not_allowed`, `insufficient_permissions`, `external_service_error`, `payment_processor_error`, `cfdi_service_error`, `internal_server_error`, `service_unavailable`, `rate_limit_exceeded`, `database_error`, `data_integrity_error`, `file_not_found`, `file_upload_error`, `invalid_file_format`. Individual handlers may emit additional endpoint-specific codes, documented per operation. example: validation_failed message: type: string example: Request validation failed details: oneOf: - type: string - type: array items: type: string description: > Present only when the handler supplies detail. Validation failures emit an array of `": "` strings. example: - 'currency: Field is required' timestamp: type: integer format: int64 description: Server time in epoch milliseconds. example: 1767225600000 securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > **Authentication Method:** HTTP Bearer token. The runtime requires the literal `Bearer ` prefix — a bare token in the `Authorization` header is rejected with `401 unauthorized`. **Header Format:** `Authorization: Bearer YOUR_API_KEY` Your API key is a JWT. Live keys operate on live data (`livemode: true`); test keys operate on isolated test data (`livemode: false`). **Get your key at:** [app.gigstack.pro/settings?tab=api](https://app.gigstack.pro/settings?tab=api) **Errors:** credential failures are answered by the authentication layer with a raw `{ "message": … }` body, not the standardized envelope — `401` for a missing, malformed or expired token, `403` for a revoked key or a plan without API access. See the `Unauthorized` and `AuthForbidden` responses. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.