Verify your setup

This check exercises the whole path your application will depend on: Stripe sends a webhook, Strent refreshes the customer, and your API key reads the result. It takes a few minutes and needs no application code.

Run the check

In the Stripe Dashboard, in the same mode as your Strent project, open Customers and add a customer. Do not add a subscription. This works in Live mode too: a customer without a subscription charges nothing.
In Strent Admin, open the project Overview. Within seconds Recent activity shows Customer created in Stripe · Updated for that customer, and the Verify your setup step in the setup checklist is complete.
Copy the customer’s ID (cus_...) from Stripe and call the runtime API with it. With STRENT_API_KEY set in your shell to the key you created:
Terminal window
```
curl https://api.strent.dev/v1/active_items/list \
  --request POST \
  --header "Authorization: Bearer $STRENT_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{"stripe_customer_id":"cus_your_customer_id"}'
```
Configuration → API keys → Runtime API examples in Strent Admin shows the same call with your project’s API URL.

The expected response is 200 with an empty list:

{ "data": [] }

That is success for this test customer: Strent has synchronized it, and a customer created without a subscription has no active items. An empty list does not by itself prove that a customer has no subscriptions, because only subscriptions that give access return items.

If the check fails

Each result points to one cause:

What you see	Cause and fix
No Customer created in Stripe line in Recent activity	Stripe could not deliver the webhook. The Connect Stripe step or Configuration → Stripe names the problem with your event destination or signing secret.
Customer created in Stripe · Failed: …	Delivery worked, but the refresh failed. The Overview lists the problem with its fix; see Recover from refresh failures.
`401 INVALID_AUTH_HEADER` or `401 API_KEY_INVALID`	The API key is missing, mistyped, or unknown. Check `STRENT_API_KEY`.
`409 CUSTOMER_STATE_NOT_READY` while the line still says Refreshing	Strent has not finished the refresh. Retry in a few seconds.
`409 CUSTOMER_STATE_NOT_READY` after the line says Updated	The customer ID or the API key belongs to another project. Use both from the project that refreshed the customer.
A network error	The API URL is wrong. Copy it from Runtime API examples in Strent Admin.

The test customer stays in Stripe and in Strent; it does not affect your application.

Continue the guide →