Ironfang Rig API
API by Ironfang · rest
Ironfang Rig gives an application under test a disposable external world: temporary inbox addresses, public callback URLs, mock HTTP endpoints and connector routes, allocated fresh for every run, with an append-only, sequenced timeline of everything Ironfang observed. The model is: suites persist, runs are disposable, resources have explicit lifetimes. A suite is a versioned definition of resources and expectations; a run is one execution of the suite's current version, lives for its TTL (default 30 minutes, at most 24 hours) and ends by being finished, cancelled or expired. Nothing here runs your code. What is billed is interactions: each accepted inbound email, inbound callback and mock exchange is one rig.interaction, counted once when it is recorded. Creating projects, suites, runs and resources, and every call to this API, is never metered. getUsage reports the meter and getEnvironment says what counts and how a refusal is answered. Everything is organisation-bound: an…
Endpoint: https://api.ironfang.com/rig
Verification: observed. Source: crawl.
Capabilities (34)
- The hosts bounds and retention a client builds against
- The keys evidence is signed with
- Tenant-scoped setup facts and recent activity for the portal
- List projects
- Create a project
- Get a project
- List runs
- Get a run
- Cancel a run
- List a run's connectors
- Mint a connector and its bootstrap token
- Read the timeline
- Get an event
- Download an event's payload
- Replay a recorded callback
- Export the run's evidence bundle
- List a run's faults
- Arm a fault
- Disarm a fault
- Finish a run
- Keep the run from retention until a date
- Lift a retention hold
- A signed receipt for the run
- List a run's resources
- Allocate a resource