Custom ecommerce

Integrate virtual try-on into a custom ecommerce stack

Custom and headless stores can integrate TryRobe through any backend capable of making secure HTTPS requests. The essential boundary is simple: the shopper talks to the merchant, and only the merchant's trusted backend talks to TryRobe with the license key.

Reference architecture

Create a merchant endpoint that authenticates the shopper or applies abuse controls, validates consent, submits the job with an idempotency key, and stores the returned job ID.

Browser or app
  → merchant API
    → TryRobe create job
      → queue and generation
    ← signed webhook
  ← merchant result endpoint

Reliability requirements

Treat job creation and webhook delivery as retryable distributed operations.

Use one stable idempotency key per user action
Persist job and product references
Verify webhook signatures before processing
Handle duplicate and out-of-order events
Keep authenticated status polling as a recovery path

Data minimization

Do not send customer image URLs, API keys, names, emails, or other personal data to product analytics. Record anonymous funnel events and internal job identifiers only when appropriate.

Frequently asked questions

Does TryRobe require a specific frontend framework?

No. React, Next.js, Vue, native mobile apps, and other clients can use a merchant backend that implements the documented API contract.

Should the browser poll TryRobe directly?

No. The browser should poll the merchant's backend so the TryRobe license key and account boundary remain protected.