IWNTA · COLLECTION BLUEPRINT

Demo store

Inspect the extracted definitions, select compatible requests, and map the responses. Nothing runs during review or import.

Definitions only · activation is separate
  1. ✓Upload collection
  2. 02Review operations
  3. 03Create inactive drafts
2Operations
2Compatible draft formats
0Need manual adaptation

What was understood — and what still needs configuration

Parsing is not execution readiness. Compatible means an inactive draft can be created, not that identity, permissions or business rules have been verified. Open each card to inspect the evidence and the exact import blockers.

Admin and staff tokens are not interchangeable. A shared Postman variable name does not prove a shared identity or permission set. Configure and verify separate credentials for each role before assigning tools to an agent.
GETList products/productsReview required
Auth: none
Body encoding: json

List the products available to the current account.

Review contract & test inputs

No input fields were detected.

Example types do not establish a schema. Imported placeholders require manual review; configure typed fields and trusted identity sources before agent use.
Inferred nested input structure

Types come from examples, not an authoritative API schema. Empty/mixed arrays remain unresolved. Required fields, constraints and identity sources need review; this structure is not enforced by the legacy executor.

{
    "type": "object",
    "properties": {},
    "required": [],
    "x-review-required": "not_a_validated_contract"
}
Response field paths (examples, not a contract)
datadata.*data.*.iddata.*.name
Review notes (3)
  • Review user identity, record ownership and authorization. Documentation does not establish permission to execute.
  • Check business rules, required fields and operation dependencies with the API owner.
  • The base URL is a variable. A safe baseUrl/base_url collection value may be suggested; verify the destination and any path prefix. Other variable values are not copied.

Enter paths relative to each result item, e.g. name and id. Verify against a real test response. Mappings are not guessed.

POSTCreate enquiry/enquiriesReview required
Auth: none
Body encoding: json

Create an enquiry after the customer confirms the subject and message.

Review contract & test inputs
FieldLocationExample typeRequired?Input source / review
subjectRequest bodystringNot determined automaticallyNot configured — user input, lookup or verified identity must be chosen
messageRequest bodystringNot determined automaticallyNot configured — user input, lookup or verified identity must be chosen
Example types do not establish a schema. Imported placeholders require manual review; configure typed fields and trusted identity sources before agent use.
Inferred nested input structure

Types come from examples, not an authoritative API schema. Empty/mixed arrays remain unresolved. Required fields, constraints and identity sources need review; this structure is not enforced by the legacy executor.

{
    "type": "object",
    "properties": {
        "subject": {
            "type": "string"
        },
        "message": {
            "type": "string"
        }
    },
    "required": [],
    "x-review-required": "not_a_validated_contract"
}
Review notes (4)
  • Review user identity, record ownership and authorization. Documentation does not establish permission to execute.
  • Check business rules, required fields and operation dependencies with the API owner.
  • The base URL is a variable. A safe baseUrl/base_url collection value may be suggested; verify the destination and any path prefix. Other variable values are not copied.
  • No usable response example was supplied.