Test mode

Every Dib team — Pro or not — can mint dib_test_* keys for free. They behave just like live keys, but every read and write targets a shared sandbox team filled with predictable fixture data.

Why use it?

• Build your integration end-to-end without risk to real data.
• Reproduce a flow against deterministic content during QA.
• Run integration tests in CI against a stable dataset.
• Showcase your app to investors / customers without exposing yours.

What's in the sandbox?

• ~30 inventory items across kitchen, living room, and garage.
• One vehicle (a 2022 Toyota Tacoma).
• Two starter tasks.
• A few rooms with placeholder photos.

Each night at 00:00 UTC Dib resets the sandbox to the canonical fixture state — anything you created during the day is wiped. Plan your tests accordingly.

How to tell them apart

• Test keys always start with dib_test_.
• Responses include X-Dib-Environment: test and X-Dib-Sandbox: true headers.

Test mode vs Live

Recommended workflow

1. Mint a dib_test_* key first.
2. Build, integrate, and add CI tests against it.
3. Mint a dib_live_* key only when you ship to production.