Send us products by API

Once we approve your application you get two keys. The test key answers with scripted results: nothing is read, listed or emailed, and it works before your account is switched on. The live key submits real products.

Send the key on every call as Authorization: Bearer <your key>. Use HTTPS only. If we agreed fixed server addresses with you, calls from any other address are refused.

POST https://www.launchscaler.com/api/partners/v1/submissions
Authorization: Bearer <your key>
Idempotency-Key: <optional, up to 128 characters>
Content-Type: application/json

{
  "url": "https://www.example.com",
  "contact_email": "founder@example.com",
  "partner_ref": "prj_4QzX1m9L"
}

• url is the product's public website. We read its name, copy, logo and pricing ourselves.
• contact_email is the founder's address. We use it for one email, on launch day, inviting them to claim the listing, and to recognise them when they sign in to claim it. We never show it publicly or return it to you.
• partner_ref is your own id for the project: letters, digits and _ . : -, up to 128 characters.

{ "id": "sub_8fK2qLx9Vb3Nm7Tz4wQa", "status": "in_progress", "badge_html": "<a href=…>…</a>" }

badge_html is our badge for this product, ready to place in the founder's footer. It lets the founder claim the listing in one click. Where your agreement with us requires our badge, a free listing goes live only once it's on the site.

Sending the same Idempotency-Key, or the same partner_ref while its submission is still active, returns the first answer with 200 and creates nothing new. After a refusal, the same partner_ref can be sent again and gets a fresh read of the website.

GET https://www.launchscaler.com/api/partners/v1/submissions/{id}
Authorization: Bearer <your key>

{ "id": "sub_…", "status": "in_progress" }
{ "id": "sub_…", "status": "submitted", "launch_date": "2026-12-01" }
{ "id": "sub_…", "status": "live", "launch_date": "2026-12-01", "live_url": "https://www.launchscaler.com/products/example.com" }
{ "id": "sub_…", "status": "not_accepted", "reason": "below_bar" }

Most products move from in_progress to submitted within an hour. A launch day can move if the founder claims the listing and picks another day; the next read, or the next webhook, shows the new date.

If you give us an HTTPS address, we POST the same body a read returns whenever it changes, with three headers:

Check the signature against the raw body, and reject a timestamp more than five minutes old. Answer with any 2xx. We don't follow redirects. A failed delivery is retried for three days with growing gaps, and you can always read the current state with a GET.

Test submissions move on their own: to submitted, with a launch day three days out, on our first run at least a minute after you send one, then to live on a run at least two minutes after that. We run every five minutes, so expect each step within about five minutes.

A test URL is never fetched, so it doesn't need to exist. To get a refusal, start the website's first label with fail. (below_bar), unreachable. or not-allowed., for example https://fail.example.com. Webhooks are sent for test submissions too, signed the same way. The live_url of a test submission is not a real page, and its badge does not draw.