https://prateeksharma.me/tags/postman/ Recent content in Postman on Prateek Sharma Hugo en-us Wed, 02 Sep 2026 00:00:00 +0000 https://prateeksharma.me/open-source/wazirx-postman-docs-sync-skill/ Wed, 02 Sep 2026 00:00:00 +0000 https://prateeksharma.me/open-source/wazirx-postman-docs-sync-skill/ <p><a href="https://prateeksharma.me/open-source/wazirx-postman-spec-alignment/">PR #7</a> fixed one concrete case of the Postman collection drifting from the live API: a wrong endpoint path and misplaced parameters on the Crypto Withdraw request. Since this collection is treated as ground truth by third-party tooling built against it, that kind of drift has a blast radius beyond the repo itself, so I turned the process I used to find and fix it into a <a href="https://github.com/WazirX/wazirx-api-postman/pull/8" target="_blank" rel="noopener noreferrer">Claude Code Skill</a> : a plain Markdown file (<code>.claude/skills/wazirx-postman-docs-sync/SKILL.md</code>) with instructions for an agent to fetch the real spec, compare method, path, parameter location, and types against each existing request, fix confirmed drift, and flag anything ambiguous rather than guess.</p> https://prateeksharma.me/open-source/wazirx-postman-spec-alignment/ Wed, 02 Sep 2026 00:00:00 +0000 https://prateeksharma.me/open-source/wazirx-postman-spec-alignment/ <p>WazirX&rsquo;s official Postman collection is what third-party tooling (SDK generators, connector wrappers, including my own) treats as ground truth, so drift between the collection and the live API has consequences beyond the collection itself. I audited every request in both collection files against the current published spec at <a href="https://docs.wazirx.com/#public-rest-api-for-wazirx" target="_blank" rel="noopener noreferrer">docs.wazirx.com</a> and fixed what didn&rsquo;t match:</p> <ul> <li><strong>Withdraw</strong> was pointing at the wrong endpoint with params in the wrong place (<code>POST /sapi/v1/crypto/withdraws</code> as query params, instead of <code>POST /sapi/v1/crypto/withdraw</code> with a signed, url-encoded body).</li> <li><strong>Create Auth Token</strong> was signing a url-encoded body instead of the query string.</li> <li>A <strong>Funds</strong> query param was typo&rsquo;d as <code>recvWindow1</code>.</li> <li><strong>New Order</strong> used <code>stop_price</code> instead of the documented <code>stopPrice</code>.</li> </ul> <p>I also added four documented endpoints that were missing from the collection entirely (address book, funds v2, wallet transfer, and wallet transfer history), following the signing conventions of the closest existing request. Open as <a href="https://github.com/WazirX/wazirx-api-postman/pull/7" target="_blank" rel="noopener noreferrer">#7</a> .</p>