Quickstart

Version Current (2026.03)

Provision MissionOS access, verify your environment, and send your first payload—this guide walks through the minimum steps for a sandbox deployment.

Prerequisites

Before you begin, confirm you have a portal URL, an administrator account, and API credentials issued for your sandbox project.

Supported browsers: latest Chrome, Edge, Firefox, or Safari.
Outbound HTTPS to MissionOS endpoints allowed from your network.
Optional: CLI or Postman for API exercises below.

Configure access

Open the admin console, create or import users, and assign roles that match how your team will review data versus operate integrations.

Single sign-on

If your tenant uses OIDC or SAML, finish the identity-provider handshake before inviting end users—failed logins are easier to debug before go-live.

Send your first request

Use the session endpoint to obtain a token, then call a read-only route to validate connectivity. Keep request IDs from responses for support tickets.

POST /v2/sessions/init with your API key.
Store the returned session token securely (memory or vault).
GET /v2/health or your product-specific ping route.

Next steps

Explore product-specific manuals from the hub, enable webhooks for asynchronous jobs, and promote the same configuration to staging when checks pass.

The hub home (Documentation hub) lists MissionOS modules and walkthrough videos without the sidebar layout used here.