Find E-Commerce Promo Code Endpoint
Budget: $30 – $250 USD
I’m working with an online retail store and need to map out the exact request that the site uses to create and validate promo codes. The storefront is a standard e-commerce build (not a marketplace or subscription model), but the underlying platform isn’t obvious from the frontend.
What I already have
– Full access to the public site from the browser
– Browser dev-tools recordings showing network traffic when a code is applied (they still feel incomplete)
– Sample promo codes that should succeed or fail
What I need from you
1. Pinpoint the precise endpoint URL the site calls when a shopper submits a promo code.
2. Document the request method, required headers, query/body parameters, and the structure of the JSON or form response.
3. Provide a quick test script (cURL, Postman collection, or lightweight Python snippet) that proves the call can be replicated outside the browser.
Acceptance criteria
• Script returns the same success / failure messages the frontend shows.
• All parameters clearly labelled so I can plug in new codes later.
• No site functionality is broken in the process (read-only testing only).
If you’re comfortable sniffing traffic, reading minified JS, or working through Cloudflare-protected flows, this should be straightforward. Let me know how soon you can turn around the endpoint documentation and test call.
What I already have
– Full access to the public site from the browser
– Browser dev-tools recordings showing network traffic when a code is applied (they still feel incomplete)
– Sample promo codes that should succeed or fail
What I need from you
1. Pinpoint the precise endpoint URL the site calls when a shopper submits a promo code.
2. Document the request method, required headers, query/body parameters, and the structure of the JSON or form response.
3. Provide a quick test script (cURL, Postman collection, or lightweight Python snippet) that proves the call can be replicated outside the browser.
Acceptance criteria
• Script returns the same success / failure messages the frontend shows.
• All parameters clearly labelled so I can plug in new codes later.
• No site functionality is broken in the process (read-only testing only).
If you’re comfortable sniffing traffic, reading minified JS, or working through Cloudflare-protected flows, this should be straightforward. Let me know how soon you can turn around the endpoint documentation and test call.