Specification libraries
Specification libraries keep REST, SOAP, and GraphQL contracts separated by protocol while sharing the same create, validate, run, inspect, regenerate, and batch workflow.
What you can do
- Create specifications manually, from fragments, through Craftsman, or from OpenAPI generation.
- Run saved assets and inspect expected-versus-received response evidence, including document hash and fingerprint checks.
- Reuse specifications in flows, Sentinel checks, snapshots, and ATF exports.
Starts with
- Protocol-specific request data and stable response expectations.
- Optional fragments, generated drafts, request attachments, and runtime environments.
Produces
- Runnable REST, SOAP, or GraphQL contracts.
- Structured run results and reusable assets for the rest of the platform.
- Document assertion metadata without persisted copies of response documents.
Use it when
- Use specifications when discovered behavior must become an explicit repeatable contract.
- Choose the protocol-specific Automation page for detailed fields and examples.
- specification
- API contract
- REST
- SOAP
- GraphQL
- document assertion
- attachment fingerprint