---
title: "Stripe Key Check"
method: GET
path: "/api/v1/dev/stripe-key-check"
tags: ["dev"]
---

# Stripe Key Check

`GET /api/v1/dev/stripe-key-check`

## Request

- Base URL: `https://api.trylapis.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.trylapis.com/api/v1/dev/stripe-key-check`
- Auth: none declared

Opt-in, read-only check of the configured STRIPE_SECRET_KEY (dev-only).

Issues ``list(limit=1)`` calls against the Stripe resources LapisCore uses
(customer portal configurations, subscriptions, invoices, checkout
sessions, customers, coupons, prices) and reports which ones the key can
read, with Stripe's own message for any it cannot. Never writes to Stripe
and is never run automatically.

Note: a restricted key needs "Customer portal: Write" for
/api/v1/stripe/billing-portal-session; a passing read probe does not prove
the write permission.

## Headers

- `x-lapis-dev-token` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-17** `a213a088ad06`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/trylapis/apis/lapiscore-api/changes/api/v1/dev/stripe-key-check/get.md)

---

[API](https://skmtc.dev/trylapis/apis/lapiscore-api.md) · [All operations](https://skmtc.dev/trylapis/apis/lapiscore-api/llms.txt) · [OpenAPI document](https://skmtc.dev/trylapis/apis/lapiscore-api/revisions/f285e7f7375a?raw)