Getting started — IngevoraMirage

Getting startedThis walk-through takes you from your first sign-in to your app's first request. It uses a face lens made from a template. You need a computer with a recent browser, and a phone for the test.1. Join a workspaceYou work in a workspace: your company's team in IngevoraMirage. The editor is at https://ingevoramirage.ingevora.com. There are two ways in.From an invitation. An Owner of the workspace invites your email address. The email is titled "‹name› invited you to ‹workspace› on IngevoraMirage". Its link works once, for 7 days.

If you have no account yet, the page asks for your name and a password, and for you to accept the Terms. Choose Create my account.

If you already have an account, choose Sign in to join, sign in, then choose Join.

By signing up. While sign-up is open, the Sign in page shows Create an account. Enter Your name, Work email and a Workspace name, tick the box to accept the Terms and the Privacy Policy, and choose Continue. You get an email with a link that works for 24 hours. It opens Create your password: choose a password, then Create my workspace. You are the new workspace's Owner.If the Sign in page has no Create an account, or the sign-up page says Sign-up opens soon, sign-up is not open yet. Ask an Owner of an existing workspace to invite you.Passwords need at least 12 characters.2. Make a face lens from a templateYou need the Owner or Designer role for this step.

Open Face lenses and choose New face lens. In an empty workspace, Create your first face lens does the same.

Under Template, pick Face accessory: a crown above the forehead.

Type a Name and choose Create. The Arabic name is optional.

The studio opens with one layer, crown, on sample art you can replace later. To see it on a face, use Choose a photo or Use my camera in the viewer. See Studio tour.3. Try it on your phoneChoose Test on phone in the studio header. Scan the QR code with your phone's camera, open the page and tap Start camera. The page draws the current draft over the front camera and follows your edits. The link works for 30 minutes, and testing publishes nothing. See Test on your phone.4. Publish version 1Choose Publish. The editor saves your edits, checks the lens on the server and, if there are no issues, publishes it. You see "Published version 1".If something needs fixing, the Issues tab lists it. Click an issue to go to its layer, trigger or clip. The Versions tab lists every published version. See Versions, latest and pinned.5. Issue an API keyYou need the Owner or Developer role for this step.

Open API keys under Workspace in the navigation.

Type a New key name, such as "production server", and choose Issue key.

Copy the key. It starts with mk_ and is shown only this once. Store it in your server's secret store, then choose I have stored it.

See API keys.6. Make your first requestOpen Developers under Workspace. In Your lenses and effects, copy your lens's id. Then call the delivery API from your server, with your key in the X-Api-Key header:

bash

curl -H "X-Api-Key: mk_…" https://mirage-api.ingevora.com/v1/lenses/8f3c2a10-…

The answer describes the latest published version:

json

{
  "data": {
    "lensId": "8f3c2a10-…",
    "version": 1,
    "manifestUrl": "https://…/lenses/8f3c2a10-…/1/manifest.json",
    "manifestSha256": "3b7e…",
    "totalBytes": 48213,
    "minEngineVersion": 1,
    "publishedAt": "2026-10-02T09:30:00.000Z",
    "previewUrl": "https://…/lenses/8f3c2a10-…/1/preview.png"
  },
  "success": true
}

A 404 means the id is wrong or the lens has never been published. A 403 means face lenses are off for your workspace. See Delivery API for every field.7. Download it safelyFetch manifestUrl and check that its SHA-256 equals manifestSha256. Then fetch each image the manifest lists, from the same folder, and check it against the sha256 the manifest gives it. Use the lens only when every check passes. See Downloading safely.Next steps

Learn what your layers can do in Face lenses and Screen effects.

Make the lens react to the face or to your app in Triggers and your events.

Plan for failures in Errors and limits.