Sandbox
A test key (gfy_test_...) lets you build and test your whole integration without spending credits. It uses the same endpoints and request fields as a live key.
What a test key does
- Returns the same sample result for any image: a score of 86 and 12 rooms. The image you send does not change the result.
- Uses no credits and no AI.
GET /v1/creditsshowsavailable: null. - Takes about 5 seconds per stage, so a simple analysis finishes in around 15 seconds.
- Test and live data are separate. A test key only sees test analyses, and a live key only sees live ones.
- Sends webhooks to your endpoint with
livemode: false.
Which review steps pause
In the sandbox Grihafy always reports low confidence about north, unless you send northAngle. That makes review steps easy to trigger.
| reviewMode | Without northAngle | With northAngle |
|---|---|---|
auto | Finishes. No pause. | Finishes. No pause. |
north_if_low_confidence | Pauses for north. | Finishes. No pause. |
rooms | Pauses for rooms. | Pauses for rooms. |
north_and_rooms | Pauses for north, then for rooms. | Pauses for rooms. |
The sample result is a single home, so the sandbox never splits a plan into flats and analyzeAllUnits has no effect.
Quickstart shows both a direct run and a run with a review step.
What still behaves like live
These checks apply to test keys too, so you can find problems early:
- Upload checks: size, file type and readability, with the same errors (
413,415,422). - The 120 requests per minute key limit and the organization queue limit.
- Idempotency keys.
What the sandbox cannot show
It does not produce a failed analysis, real scores for your floor plan, translated reports, or the review expiry. Handle those from this documentation and check them in a live trial. See Going live.