Sandbox Basics

A sandbox is a working APIANT system you can build, test, and break things in safely. It runs the same engine as production with looser limits and no real customers downstream.

What's there from the start

A fresh sandbox has the catalog of all built-in connectors APIANT ships, ready to use as soon as you provide credentials for the services you want to integrate. The plugin is set up to talk to the sandbox automatically once you've completed /apiant-setup.

The catalog is shared infrastructure. New connectors and connector updates land in your sandbox automatically, the same way they land in production.

What you have to set up yourself

A fresh sandbox has no pre-registered OAuth apps. To integrate with an OAuth-only service, you have to register a developer application with that service first; Claude walks you through it with dev-browser, reading the live developer-portal page beside you. See App Connectors for the full walkthrough. Most non-OAuth services in the catalog work as soon as you paste an API key into the keyvault when Claude prompts you.

Per-tenant data — automations you build, connections you create, keyvault entries, automation execution history — is yours to manage. Nothing seeds the sandbox with sample automations.

Cleaning up sandbox state

APIANT has no single "reset sandbox" button. Cleanup is per-object: you remove the things you no longer want and leave the rest. What's available:

• Reset an automation. The automation's right-click menu has a Reset... option that flushes the automation's stored row identifiers and any unprocessed webhook payloads in its work queue. After a reset, polling automations rebuild their identifier set on the next run and only sync newly created records going forward; previously synced rows stop mirroring. Webhook, web-service, and widget triggers reset immediately without the rebuild step.
• Clear an automation's stored data. The Inspect stored data menu opens the automation's keyvalue store; you can delete entries individually. Dump stored data exports the whole store as a download for review.
• Delete an automation. Removes the automation, its assembly instances, its keyvalue entries, and its webhook routings. The platform refuses the delete if the automation is referenced by other automations and tells you which ones — break those references first.
• Delete a connection. Connections (keyvault credential entries) are removed individually from the keyvault UI. There's no bulk-wipe.
• Automation execution history ages out automatically based on the system's maxAutomationLogAgeDays setting.

If the sandbox is in a state none of the above can recover from — corrupted system data, a failed migration, anything that warrants starting over — contact APIANT support to refresh the tenant. There is no self-service equivalent.

When something doesn't work

Issues specific to sandbox state, not plugin install:

Connection refused after a long idle

If your sandbox sits unused for a long stretch and then errors on the first request, the most common cause is an OAuth token that expired while you were away. Ask Claude to re-authenticate the affected connection, then try again. Persistent failure with a fresh token is a real outage; check your APIANT URL in a browser.

A test run hangs and never completes

An execution stuck mid-run usually means one step is waiting on an external service that isn't responding. Halt the execution from the automation's history view (or ask Claude to halt it), then look at the last completed step to see what it was waiting on.

Stored data doesn't match what you expect

Two-way sync automations rely on identifier sets in the keyvalue store to decide what's new versus what's already mirrored. If you've deleted records on the external side and want APIANT to re-discover them, Reset... the automation. If you've manually added records and want APIANT to skip them, the keyvalue store is editable through Inspect stored data.

Plugin or connection issues

Anything plugin-side — skills not appearing, /apiant-setup failing, version mismatches — is covered in Install the Plugin. Start there before assuming sandbox state is the problem.

What to read next

• Building with the Plugin — every skill the plugin offers, organized by task
• API Authentication — set up your first credential and build a real integration