API Collection Builder
Package approved cases into a portable, environment-safe collection.
Inputs and evidence
Require approved cases or contract-backed request details, the requested collection format,
and documented assertions. List unknown base URLs, auth sources, variables, and cleanup rules
as unresolved inputs.
Workflow
- Map each approved case to one request; preserve its traceability ID.
- Parameterize base URL, authentication, resource IDs, and environment-specific values.
- Add only contract-backed status, header, and body assertions.
- Capture documented response values for dependent requests and add cleanup only when its
operation and ownership are confirmed.
- Validate artifact syntax and provide a case-to-request mapping plus run prerequisites.
- HUMAN REVIEW GATE (mandatory). Stop before executing the collection; request approval
of the environment, credentials source, write operations, request volume, and cleanup.
Output shape
- Requested collection artifact
- Secret-free environment template
- Case-to-request traceability table
- Unresolved variables, assumptions, and run command
--- HUMAN REVIEW GATE --- with approval status
Guardrails
- Never embed credentials, tokens, real customer data, or secret example values.
- Never invent an endpoint, field, assertion, dependency, or cleanup operation.
- Never report requests as passing without supplied runner evidence.
- Do not execute writes, deletes, or live requests without confirmed authorization and target;
default to generating the draft only.
1---2name: api-collection-builder3description: Convert approved API test cases into a Postman/Newman or Bruno collection. Use when asked to build an API collection, make cases runnable in Newman or Bruno, parameterize environments, or package requests, assertions, chaining, and cleanup. Produce a reviewable execution artifact rather than redesigning API coverage.4license: MIT5---67# API Collection Builder89Package approved cases into a portable, environment-safe collection.1011## Inputs and evidence1213Require approved cases or contract-backed request details, the requested collection format,14and documented assertions. List unknown base URLs, auth sources, variables, and cleanup rules15as unresolved inputs.1617## Workflow18191. Map each approved case to one request; preserve its traceability ID.202. Parameterize base URL, authentication, resource IDs, and environment-specific values.213. Add only contract-backed status, header, and body assertions.224. Capture documented response values for dependent requests and add cleanup only when its23 operation and ownership are confirmed.245. Validate artifact syntax and provide a case-to-request mapping plus run prerequisites.256. **HUMAN REVIEW GATE (mandatory).** Stop before executing the collection; request approval26 of the environment, credentials source, write operations, request volume, and cleanup.2728## Output shape2930- Requested collection artifact31- Secret-free environment template32- Case-to-request traceability table33- Unresolved variables, assumptions, and run command34- `--- HUMAN REVIEW GATE ---` with approval status3536## Guardrails3738- Never embed credentials, tokens, real customer data, or secret example values.39- Never invent an endpoint, field, assertion, dependency, or cleanup operation.40- Never report requests as passing without supplied runner evidence.41- Do not execute writes, deletes, or live requests without confirmed authorization and target;42 default to generating the draft only.
PramodDutta