Trace the Ignition 8.1 API, version by version.
Follow the safeguards, discovery tools, and live Gateway workflows added over time. Newest capabilities appear first.
Current signal
API v0.3.149 online
59
documented actions
v0.3.149
current API
8.1.x
Ignition target
Selected documented milestones
Every release tightened the feedback loop.
A curated capability history grounded in the current API reference. Scroll down to follow the build backward.
- v0.3.149Current
Controlled resource operations
Structural inspection and recoverable project-resource deletion
The API can inspect one Vision window resource without claiming runtime proof, and can remove one manifest-backed project resource only after a dry-run, state-hash check, exact confirmation, and rollback backup.
- Bounded Vision window structure and serialization diagnostics
- State-drift protection before confirmed resource deletion
- Backup, absence verification, project scan, and normal rollback support
- v0.3.148
Perspective runtime and assets
The API moved beyond static project files
AI agents gained controlled visibility into live Perspective sessions, pages, and view instances, plus guarded management for Gateway-level themes, fonts, and icon libraries.
- Tokenized session, page, and live view discovery
- Verified session termination with dry-run and confirmation
- Theme, font, and icon-library backups outside project resources
- v0.3.145
Post-write validation
Apply began checking the final destination, not only the package
Project Library scripts, Named Queries, and Perspective page configuration are validated again after mutation and before backup finalization or project scan.
- Final-state checks for copied scripts and Named Queries
- Merged page-config validation before a change is considered complete
- Structured failure metadata for invalid destination state
- v0.3.140-0.3.142
Resource integrity
Imports learned to reason about the resource that will actually exist
The API validates final merged manifests before writing and prunes stale optional Perspective view files that no longer belong in an overwrite.
- Final merged-resource manifest validation
- Stale optional view-file pruning with explicit reporting
- Rollback manifests include files an incoming package intentionally omits
- v0.3.136-0.3.137
Stronger evidence
Project scans and historian checks became harder to misread
Changed-file operations now use a defensive second bounded scan wait, while history probes name their Count result as good-quality stored-sample evidence.
- Two bounded post-write scan waits when files changed
- Explicit scan-attempt and completion metadata
- Good-quality historian sample counts instead of ambiguous availability wording
- v0.3.114-0.3.115
Mutation safety
Concurrent writes and partial failures gained a recovery contract
Tag and UDT writes joined the Gateway-wide mutation lock, and mid-write failures began returning the backup, failed stage, written paths, and rollback availability.
- One mutation lane across project, tag, and UDT changes
- Retryable busy responses instead of overlapping writes
- Recovery metadata when a failure happens after writing begins
- v0.3.104-0.3.105
Self-maintenance
The API could update itself without giving up the way back
Self-update backups became exact-source rollback artifacts, and write workflows gained a validated, bounded project-scan timeout.
- Exact pre-update doPost and resource metadata backups
- Rollback restores both source and sibling resource metadata
- Caller-controlled scan timeout bounded from 1 to 30 seconds
- v0.3.96-0.3.99
Bounded data access
Read-only no longer meant unbounded
Alarm, audit, journal, and Named Query previews gained backend work limits so a small response cap could not hide an expensive broad query.
- Narrow source or path filters for alarm evidence
- Bounded audit and journal time windows
- Only outer-query numeric limits prove a Named Query preview is capped
- v0.3.84-0.3.92
Operational foundation
Rollback, environment portability, and session results became explicit
A unified file-change backup format made newly created files reversible, path overrides made both runner variants portable, and Perspective session caps became measurable.
- Unified fileChanges-v1 manifests for mutating file operations
- Environment overrides for Gateway and project data paths
- Matched-count and truncation evidence for Perspective sessions
- v0.3.78-0.3.83
Diagnostics and discovery
The agent gained enough runtime context to stop guessing at scale
Performance diagnostics, tag browse totals, alarm shelving context, and direct-paste fixes made discovery useful for real Gateway troubleshooting.
- Perspective and Gateway performance diagnostic actions
- Tag browse returned-size, total-available, and truncation metadata
- Alarm status could include shelved-state context
- v0.3.52-0.3.55
Project-aware building
Named Queries and module versions entered the page-building loop
Generated Perspective work could declare and validate Named Query dependencies, preview controlled query shapes, and inspect installed Gateway module versions.
- Explicit Named Query dependencies during package apply and validation
- Controlled preview rules for unsafe Named Query parameter types
- Gateway module name, version, state, and license-status discovery
The pattern behind the versions
Add capability. Add bounds. Try to break it. Keep the evidence.
The API grew around real Ignition work: inspect first, dry-run mutations, require explicit confirmation, verify the result, and preserve a recovery path when the target changed.
Put the current API and tested Ignition skills in your agent's workflow.
Lifetime access includes the current Ignition 8.1 toolkit and future releases, including Ignition 8.3 skills as they are completed.