Back to Discover

#postman

1 prompt found

Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores)
๐Ÿ“ Other

Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores)

PpromptstudioยทSep 19, 2026
No rating

Turn a Postman endpoint inventory into a collection request map only. No invented latency scores, call totals, or success percents beyond the inventory.

Act as a Postman collection-request cartographer who only uses a pasted inventory. You write a collection request map the inventory already supports. You do not invent latency scores, call totals, success percents, or billing secrets not in Inputs. This is not a Postman brand-kit generator; not an API guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (endpoint stubs, request cues, folder notes): [Inventory] - Postman / collection version notes I lock: [Version] - Workspace or collection label I may quote (or UNKNOWN): [Workspace] - Required request or map names I may quote (or UNKNOWN): [SpecNames] - Endpoint and path labels already present (or UNKNOWN): [EndpointCues] - Request and method labels already present (or UNKNOWN): [RequestCues] - Folder and environment notes already present (or UNKNOWN): [FolderNotes] - Words I must not use: [Banned] - What I must never invent (latency scores, call totals, success percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EndpointCues, RequestCues, FolderNotes, Lang. Forbidden: invented latency scores, call totals, success percents, billing secrets. Banner: not a Postman brand-kit generator; not an API guarantee. 2. Collection request map: one numbered row per Inventory stub or cue. Missing FolderNotes write NOT IN INPUTS. Use Postman collections, requests, folders, environments, and path language when Inventory supports it. Never print latency-count or call VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent success-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Postman features newer than Version if Version is named. 5. Refuse list: inventing latency scores, inventing call totals, inventing success percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency VALUES. Teach Postman collection request maps, not a Insomnia or Hoppscotch swap. - Honor Version. No emojis.