- What you receive
- requests.http — ordered VS Code REST Client request definitions; catalog.json — validated normalized collection input; README.md — client review guidance, supported profile and use rights; gateway-manifest.json — added by canonical delivery with member SHA-256 hashes. Private access follows the service-specific retention terms.
- Input required
- Use the exact hosted input schema and purchase.request example.
- Output
- requests.http — ordered VS Code REST Client request definitions; catalog.json — validated normalized collection input; README.md — client review guidance, supported profile and use rights; gateway-manifest.json — added by canonical delivery with member SHA-256 hashes
- Pricing basis
- Price per completed job. Review supported inputs, processing scope and live availability before checkout.
- Availability
- Wallet API available. Review the exact quote before payment. Browser checkout is separately qualified.
Browser checkout: available.
- Product ID
http-request-collection-bundle
Scope & limitations
- Upload strict UTF-8 JSON with collectionName and requests. Each request requires id, method and url, with optional body. These are completed request definitions; no endpoints, business rules or authentication data are inferred. Unsupported fields, duplicate JSON keys and prototype-related keys reject before checkout.
- 1–25 requests and at most 256 KiB input. collectionName is nonblank single-line text up to 120 UTF-16 code units. IDs are 1–64 ASCII letters/digits/underscores, beginning with a letter, excluding reserved prototype names, and unique ignoring ASCII case. Input order is preserved.
- Methods are uppercase GET, HEAD, POST, PUT, PATCH or DELETE. GET/HEAD cannot have a body. Other methods may supply an object-valued JSON body with nested JSON values; arrays or primitives at the body root reject. Body string values are at most 131072 UTF-16 code units; object keys are nonblank single-line text up to 240. Canonical parser depth, number, Unicode and 256 KiB bounds also apply. JSON bodies are compact single physical lines, with CR/LF/TAB escaped as data.
- URLs are absolute ASCII HTTPS DNS URIs up to 2048 normalized characters without credentials, IP literals or fragments. Percent-encode brackets, vertical bars, carets and other non-URI data. Invalid percent escapes/UTF-8, encoded controls, client-variable syntax and common credential field/query names reject. The credential-name check cannot identify every secret; do not upload secrets or personal customer data. URL reachability, ownership and safety are not checked.
- Produces the declared VS Code REST Client .http subset: ### separators, # @name identifiers, fixed Accept: application/json and optional body Content-Type: application/json. No user headers, authentication, cookies, variables, response chaining, scripts, events, environment files, servers, request execution, fetching or application imports. Review client behavior and ambient client settings before running any request; HTTP calls may change remote data or incur charges. No provider certification or universal compatibility guarantee.
- Exactly three generated files, each at most 2 MiB and together with path names at most 2 MiB before the canonical manifest. Delivery retains the existing 4 MiB ZIP and 64-member ceiling. These are processing bounds, not payment limits.
- Nonexclusive buyer's own personal or internal business use only. Standalone resale, redistribution of Gateway source or templates, and sublicensing are not permitted. Customer-provided data and pre-existing rights remain with their owners; the buyer must have permission to use supplied URLs/data and preserve applicable third-party rights. No open-source license is granted.
- USD 19.00 per one-time prepared ZIP; no subscription. Save the ZIP before its disclosed expiry.
Technical references
Qualified hosted service; current wallet availability checked at discovery