Integration diagnostics
What the console can tell you about your integration, and what you can fix from it without asking anyone.
Open your product's Integration tab. The first panel is Integration health: one line per surface, from data Guiru already has. No inference, no model, no score.
- API keyslive / test, last request
- *Healthy — last request 12 min ago*. *Live key created, never used*. *Test key only* is a warning only when the product actually gates access with the API.
- Sign in with Shin IDconfigured, last sign-in
- *Configured — no sign-in yet* is not a problem.
- Entitlementslast check
- *No successful entitlement request has been received with the live API key* — exactly that, when it is the case. *Not needed for this delivery method* when buyers are sent to a URL.
- Usagesignals in 30 days, last one
- *No activity received yet* stays neutral unless the product is Included with Member, where usage is what pays you.
- Webhookslast success, failures
- *Last delivery returned HTTP 401* rather than *webhook error*. Retrying and dead deliveries are counted.
- PayoutsStripe Connect
- Only with a paid offer: *No payout account*, *onboarding not finished*, *ready to receive money*.
What you can do from there
- Retrya dead delivery of your product
- The same payload, back in the queue; delivered within a minute. Safe by contract: delivery is at-least-once.
- Send testan endpoint of your product
- A real
webhook.testdelivery, signed with your secret, sent by the same worker, visible in the same list with its status code. Five per ten minutes. - Rotatean API key
- A new key shown once; the old one keeps working for 48 hours so a deploy has time to land.
- Refresh Stripe statusyour payout account
- Asks Stripe again whether charges are enabled.
Every action writes the same audit row an operator's would. Who may: a verified builder of the product, or a team member with the *developer*, *admin* or *owner* role. Nothing here reaches another product or an operator capability.
When it is still wrong
*Something wrong? Tell us* on the health panel files a report with your route, build, viewport and a snapshot of this panel attached, so the person who reads it does not start by asking what you see. That is the door for integration problems; product reports (spam, fraud) go through Trust & safety.