Wishlink

Wishlink is an Indian creator monetisation platform. Creators on Instagram and YouTube build a shop of product links, their audience buys on the brand's own site, and the creator earns commission. For a brand, Wishlink is a traffic and attribution partner rather than a marketplace: no order is placed on Wishlink, no listing lives there, and there is no seller panel with inventory in it. What Wishlink needs from a brand is a way to tell it which sales a given creator drove. That is done by a bespoke server-side integration agreed with Wishlink, not by a documented public API, and Wishlink publishes no developer portal.

At a glance

What it is

Wishlink is a Gurugram based creator commerce company, registered at "4th Floor, Plot No 48, AIHP Executive Centre, Sector 32, Gurugram". Its own site claims 250 or more brand partners and 15,000 or more creators as of 2026-09-21, across fashion, beauty, home decor, lifestyle and travel, with creator followings from 50 thousand to over 2 million. It runs consumer apps on both stores, and a product called Wishlink Engage that automates comment replies and sends product links by direct message.

The commercial model is outcome based. Wishlink's brand page states "We believe in results and charge you only for outcomes", with the outcome metric, sales or traffic, agreed per brand. That is the important structural fact for a connector: Wishlink bills on your sales data, so the integration exists primarily so Wishlink can see and invoice against your orders.

Wishlink is social commerce, not a marketplace. It sits alongside GlowRoad and Hypd in the Indian creator and reseller category, and Unicommerce lists it in the marketplace section of its integrations directory with the description "Wishlink provides creators with opportunities to collaborate with the brands they genuinely love", which is a channel listing rather than evidence of an API.

API access

There is no public API and no developer programme. The evidence, all checked on 2026-09-21:

• docs.wishlink.com does not resolve.
• api.wishlink.com resolves and responds, behind Cloudflare, returning a plain HTML "Not Found" page for the root with x-frame-options: DENY and referrer-policy: same-origin, the default headers of a Django application. It is the backend for Wishlink's own apps, not a documented partner surface, and nothing about it is published.
• brand.wishlink.com and creator.wishlink.com both serve the single page application shells for the brand and creator panels. Both require login.
• engineering.wishlink.com exists but returned HTTP 403 to non-browser clients.
• Nothing on wishlink.com links to API documentation, a partner developer page or an integration guide.

What Wishlink does publish about integration is a single sentence on its brand page: "Given transactions get closed on your website, we will integrate with your backend to track sales driven by each influencer on your platform." It adds "It just takes 5 mins to integrate!". Taken together with the absence of a pixel or tag manager snippet anywhere on the site, that describes a server-side integration built for each brand by Wishlink's team, most likely a link between your order data and their creator attribution. Assume a short technical call and a bespoke spec, not a key and a reference.

Authentication

Not published. No auth model, token format, header or credential lifetime appears in any public source. Whatever Wishlink issues will come out of the onboarding call.

Objects we can read

None through a documented interface.

The brand dashboard, described on Wishlink's site as a "Cutting-edge Brand dashboard" showing "results and ROI in real time", exposes funnel metrics rather than commerce objects. Wishlink's own FAQ wording is: "We track data at each step of funnel - from views and engagement to Click-Through-Rates and Conversion. You will be able to calculate RoAS, CPV, CPC."

That gives, at best:

Sample responses cannot be given because no response format is published.

Writing back: listings, price and stock

Not applicable and not available. Wishlink has no listing, price or stock object. Creators link to live product pages on your storefront, so your own site is the source of truth for price and availability, and any staleness in a creator's link is resolved by your site, not by a feed to Wishlink.

The one thing a brand does push is order and sales data, and even that is defined by Wishlink during onboarding rather than by a published contract.

Webhooks and notifications

Not published. Given the direction of the integration, the plausible shapes are that you post orders to a Wishlink endpoint as they complete, or that Wishlink pulls from an endpoint you expose. Which one applies should be the first question on the onboarding call, because it decides whether Wishlink needs a credential from you or you need one from them.

If neither exists, the fallback is the brand dashboard and a scheduled manual export, at whatever cadence your commercial reporting needs, typically weekly.

Rate limits and pagination

Not applicable. No public API, therefore no published quota, header or pagination model.

Mapping to the unified model

Wishlink does not produce objects that map onto the unified model. It annotates objects you already have. The useful shape is an attribution table alongside orders, not a second copy of orders.

The field worth adding to your own schema is an attribution column on orders: the creator identifier and the Wishlink campaign or link id that drove the sale, captured from the landing URL at checkout. That is data you can own regardless of what Wishlink ever exposes, and it makes the relationship auditable from your side.

Gaps and open questions

• The exact integration mechanism. "We will integrate with your backend" could be a REST callback, a shared database view, a nightly file, or a Shopify app. No public source says which, and the "5 mins to integrate" claim suggests something lighter than a bespoke build, possibly a script or an app for common storefronts.
• Whether Wishlink publishes a Shopify app. Nothing on its site names Shopify, but almost every Indian creator commerce company of this size has one, and it would be the fastest route to a supported integration.
• Whether the brand dashboard has an export or a read API behind it. brand.wishlink.com is a single page application, so it necessarily calls JSON endpoints on api.wishlink.com, but those are undocumented, unversioned and not offered as a contract. Using them would be reverse engineering, not integration.
• How returns and cancellations affect attributed sales and therefore fees. This is a commercial term to settle in writing.
• Whether Unicommerce's Wishlink integration involves an API or a manual channel setup. Unicommerce lists Wishlink among its marketplace integrations, which implies some machine interface exists for at least one partner, but Unicommerce publishes no technical page for it.

Sources

• Wishlink homepage, for the creator and brand propositions and the published scale figures: wishlink.com
• Wishlink brand page, the only public statement of how integration works and the source of the quoted sentences on backend integration, funnel tracking and outcome based pricing: wishlink.com/w/brand
• Unicommerce integrations directory, which lists Wishlink as a marketplace integration with the quoted creator collaboration description: unicommerce.com/integrations
• Live probes on 2026-09-21: api.wishlink.com returns HTTP 404 with Django default security headers behind Cloudflare, docs.wishlink.com does not resolve, brand.wishlink.com and creator.wishlink.com return login shells, engineering.wishlink.com returns HTTP 403 to non-browser clients