Flicker Fox Partner Sandbox Console

Tutorial: Your First Sandbox Run

Follow these steps in order. Each step builds on the last. If you have not minted credentials yet, start at Developer Account.

  1. Get Sandbox Credentials — Register and verify at /developer/account, then mint Flicker Fox sandbox credentials. You receive a value formatted partner_key:credential.
  2. Paste Auth Below — Enter that value in Sandbox Auth Value. Tapestry never stores it server-side; it stays in this browser tab only.
  3. Start a Sandbox Session — Click Start Sandbox Session. A successful response returns a stable run_id.
  4. Generate an Artifact — Run Generate Job Ad or Generate Weather Report using that run_id.
  5. Review the Inspector — Confirm the Sandbox Call Inspector shows the request, response, and correlation_id for TPCS evidence.
  6. Share Evidence — Send your operator the run_id, correlation_id, and inspector output for TPCS-T-002 review.
Protected Mode (Demo Only) — If you are demoing WordPress origin handoff and report return, use Flicker Fox Protected Mode. Most integrators on this page should stay on the sandbox workbench above.

Self-Test Checklist (TPCS)

  1. Paste Sandbox Auth — Operator-issued or self-serve value (partner_key:credential).
  2. Start Sandbox Session — Capture run_id.
  3. Generate Artifact — Job-ad or weather artifact for that run_id.
  4. Confirm Inspector Output — Success envelope with stable run_id and correlation_id.
  5. Share Evidence — Send output to your Tapestry operator for TPCS-T-002 review (no live ecosystem traffic).

Your Progress

Paste sandbox auth to begin. The fields below update as you complete each tutorial step.

Partner Key (paste auth to detect)
Certification Step Auth Required
Run ID —
Last Correlation ID —

Sandbox Credentials and API Calls

Use the fields and buttons below to exercise /v1/sandbox/flicker-fox/* on this workbench.

Start Sandbox Session

Run session start first to obtain a run_id. Generate artifacts and copy generate snippets only after this step succeeds.

Sandbox Run ID: (None Yet)

Copy Snippets for Your Terminal

Each snippet includes your current auth value and run_id when available.

Auth Header Line Single header line for curl, Postman, or HTTP client imports.
Curl — Session Start Creates a sandbox session and returns a run_id.
Curl — Job Ad Generate Requires a run_id from session start. Generates a job-ad artifact.
Curl — Weather Generate Requires a run_id. Generates a weather-report artifact.
Python Self-Test Script Standalone script with your base URL and sandbox auth pre-filled. Download and run locally — no Tapestry repository or SDK install required.

Generate Artifacts

Requires a run_id from session start above.

Sandbox Call Inspector

Sandbox Call Inspector — Waiting for Your First Request

Nothing has been sent yet. When you run a sandbox API call from this page, you will see:

  • HTTP method and path Tapestry received
  • Request headers (auth redacted) and JSON body
  • Response status and JSON envelope
  • correlation_id for support and TPCS evidence

Next step: paste your sandbox auth above, then click "Start Sandbox Session".

API Reference

These pages document the contract. They load even before you run calls on this workbench — use them while you follow the tutorial.

Related Surfaces