MakeO

makeO is a single-brand Indian clear aligner and skin clinic business, not a channel. No seller API; api.toothsi.in is an undocumented AWS API Gateway behind its own apps.

makeO is an Indian direct-to-consumer health and beauty business operated by MakeO Healthcare Technologies Pvt. Ltd. It runs two brands: toothsi, which sells clear aligners and oral care, and skinnsi, which runs laser hair removal, skin and hair clinics. Most of what it sells is a clinical service with a physical product attached, delivered through its own clinics, at-home scans and franchise partners. It is a brand, not a marketplace: there is no seller account, no third-party listing surface and no public API. The one page on the site called "technical document" is a patient instructions-for-use document for a regulated medical device, not API documentation.

At a glance

What it is

MakeO Healthcare Technologies Pvt. Ltd. describes itself in its own footer as "An ISO 13485:2016 Quality Management System certified by Zenith Quality Assessors Pvt Ltd and US FDA Cleared". ISO 13485 is the medical device quality standard, which is the right framing for the whole business: makeO is a device and clinical services company that also sells consumer products, not a retailer.

Two brands sit under it:

toothsi, clear aligners, teens aligners, braces, retainers, teeth whitening, scaling, oral hygiene products, aligner essentials and bundles, plus an "AI Powered Smile Tracker" and a "toothsi at home" scan.
skinnsi, laser hair removal across body areas, hydrafacial, acne treatment, laser toning, anti-ageing, body polishing, derma facial, PRP and other hair fall treatments, plus skincare products.

Delivery is physical and local. The site lists clinic and at-home scan coverage in Ahmedabad, Bangalore, Pune, Mumbai, Chandigarh, Chennai, Delhi NCR, Faridabad, Ghaziabad, Gurugram, Guwahati, Hyderabad, Indore, Jaipur, Noida, Kolkata, Surat and Nagpur, and there is a separate makeO UAE presence. Site navigation includes "become a franchisee", "partner clinics" and a doctor partner form at /toothsi/doctor-partners.

Note

The revenue here is mostly a treatment plan, not a basket. An aligner case is a scan, an orthodontist prescription, a manufactured series of trays keyed to a patient, a wear schedule and a retention phase. The unified model's orders and order_items describe the oral care products makeO also sells, but they do not describe the aligner business, which is the bulk of it. Classifying makeO as a sales channel will produce a connector that sees the small half of the company.

API access

None public. Checked on 2026-09-22:

api.makeo.app, docs.makeo.app, partner.makeo.app, seller.makeo.app, makeo.in and makeo.co do not resolve.
makeo.app is the live site, a Next.js application. makeo.me resolves to a CloudFront distribution and is referenced from the main site, most likely for short links or the app.
api.toothsi.in resolves and returns HTTP 403 with the body {"message":"Missing Authentication Token"}. That is the exact signature of Amazon API Gateway rejecting an unsigned request to an unmatched route. It is the backend for makeO's own applications. Nothing about it is documented, versioned publicly or offered as a contract, and using it would be reverse engineering rather than integration.
Static assets are served from assets.toothsi.in and asset1 through asset3.toothsi.in, so the toothsi domain remains the technical home even though the consumer brand has moved to makeO.
makeO appears in neither EasyEcom's public knowledge base nor Unicommerce's integrations directory.

The page at /toothsi/technical-doc, titled "Technical Doc", is worth calling out because its name invites a wasted click. It is the patient instructions for use for the aligner device, covering wear time of "16-18 hours daily including your sleep", how each aligner is "engraved with the first four letters of your name, a 'U' for upper teeth or an 'L' for lower teeth, followed by the stage number", cleaning with Toothsi Foamy, insertion, and what to do on an allergic reaction. It is a regulatory document, and it contains nothing technical in the software sense.

Authentication

Not published. The site has consumer accounts and an app. There is no partner or developer credential.

Objects we can read

None through a documented interface.

No sample responses can be given, because no response contract is published.

Writing back: listings, price and stock

Not available. makeO sells its own brands through its own channels. There is no seller onboarding, no catalogue upload and no feed specification.

The two partner routes that do exist are commercial, not technical:

Franchise. "Become a franchisee" for a skinnsi or toothsi clinic. A franchisee operates makeO's system; it does not list products into it.
Doctor partners. A form at /toothsi/doctor-partners collecting first name, last name, mobile and an intent option. This is clinician recruitment, not a data interface.

If you are a supplier wanting your product in makeO's oral care or skincare range, that is a procurement conversation with MakeO Healthcare Technologies, ending in a purchase order.

Webhooks and notifications

None. Nothing to subscribe to and nothing to poll.

Rate limits and pagination

Not applicable.

Mapping to the unified model

No public schema exists, so no field mapping can be given honestly. The structural notes that matter if this is ever revisited:

Gaps and open questions

Whether makeO sells through any third-party marketplace, which would make it reachable through that marketplace's API rather than its own. Its oral care and skincare products are the kind of thing that usually lists on Amazon, Nykaa and Flipkart, and none of that was verified here.
Whether a franchisee gets any machine-readable view of their clinic's bookings and sales. A franchise network of this size almost certainly has a partner portal; nothing public describes it.
What api.toothsi.in serves. It is the applications' backend and is not offered publicly, so this is curiosity rather than integration.
The makeO UAE entity and whether it is a separate company with separate systems.
Whether makeO is in the channel catalogue by mistake. A single-brand clinical services company with no seller programme is not a sales channel, and the entry is worth confirming with whoever added it.

Sources

makeO homepage, the source for the brand structure, the toothsi and skinnsi service lists, the city coverage, the franchise and partner clinic navigation, and the footer entity "MakeO Healthcare Technologies Pvt. Ltd." with its ISO 13485:2016 and US FDA statements: makeo.app
makeO toothsi technical document, the patient instructions for use quoted above: makeo.app/toothsi/technical-doc
makeO doctor partners form: makeo.app/toothsi/doctor-partners
Live probes on 2026-09-22: api.toothsi.in returns HTTP 403 with {"message":"Missing Authentication Token"}, the Amazon API Gateway signature; api.makeo.app, docs.makeo.app, partner.makeo.app, seller.makeo.app, makeo.in and makeo.co do not resolve; makeo.me resolves to a CloudFront distribution
Unicommerce integrations directory, which does not list makeO: unicommerce.com/integrations