Playground and Test Calls
Run the first consent-scoped test call, inspect the response, and confirm the lookup lands in the audit log before production review.
The playground exists to prove the response, scope, and audit trace are all correct before live traffic starts.
Test calls and signed event verification should stay in the same operator lane.
A good playground page makes the next production-review step obvious instead of sending teams back into docs.
Confirm HRS, consent scope, and event history come back exactly as the project expects.
It shows the request shape, the returned HRS payload, the consent metadata, and the audit trace recorded for that test call.
The goal is not just to see a successful response. It is to understand the exact scope and contract the integration will rely on.
From there the project can move through production review with much better operational confidence.
The first live test should prove the subject payload and consent fields are wired correctly.
Signed event verification belongs in the same testing lane as the response itself.
A clean first call should move directly into production review instead of back into docs.
The playground should prove the project, key, and response shape are all aligned.
A clean test call should feed directly into the live approval lane.
The operator should know the request and webhook trace already landed in the audit history.
The playground is the fastest way to verify that the project, key, consent scope, and declared purpose are wired correctly.
It shows the request shape, the returned HRS payload, the consent metadata, and the audit trace recorded for that test call.
Teams usually review the current HRS, trend direction, consent timestamp, and the permitted event history fields before they wire the same response into their product.
The goal is not just to see a successful response. It is to understand the exact scope and contract the integration will rely on.
Once the first request lands, teams usually attach webhooks, verify retries and signatures, and then use the platform dashboard to monitor usage and alerting.
From there the project can move through production review with much better operational confidence.