> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/billing/stripe-config

> Return the current organization's Stripe publishable-key configuration for browser payment setup

Return the current organization's Stripe publishable-key configuration for browser payment setup

<Info>
  Audience: application and coding agent.
</Info>

## Response shape

* `publishableKey` is the non-secret Stripe publishable key for the organization's current billing mode.
* `publishableKey: null` means browser payments are not configured for that mode; render a payments-unavailable state instead of calling Stripe Elements.
* `livemode` tells the browser whether the key is for live or test Stripe mode.

## Canonical metadata

* `requestId`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/billing/stripe-config"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "stripe_config",
    "publishableKey": "pk_live_example",
    "livemode": true,
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/billing/stripe-config to return the current organization's Stripe publishable-key configuration for browser payment setup. Preserve `requestId` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff