Getting Started

Getting Started with New Instancelink

New Instance is a multi-product developer platform. This documentation covers the supported REST endpoints and product integration guides.


Productslink

ProductHow it integratesWhere to find it
BugWatchREST API + SDKs — error/log ingest, enrichment, OpenTelemetry, symbols, CI deploymentsIngest & Errors, SDK Usage & Event Enrichment, Browser & Mobile, Source Maps & Symbols, OpenTelemetry, Prometheus & Tracing, Deployments (CI/CD), SDK & CLI Directory
Support TicketsREST API — mint sign-in links, create/read tickets + comments; outbound ticket webhooksSupport Tickets, Webhooks
Secret ManagerREST API + nism CLI — fetch encrypted secrets at runtimeSecret Manager
ChatEmbeddable web widget + native mobile SDKs (Android, iOS, Flutter, React Native)Chat
Docs PortalDashboard-managed documentation publishing (OpenAPI/Postman import, custom domains)Docs Portal
AI Agent AccessMCP endpoint — let AI agents query your data with your API keyAI Agent Access (MCP)

Cross-cutting references: Webhooks — Receiving Platform Events, Errors, Rate Limits & Troubleshooting, Go-Live Checklist, End-to-End runnable flow.


Create your account and organisationlink

  1. Sign up at https://www.newinstance.cloud — this creates your account.
  2. Log in to the merchant dashboard at https://app.newinstance.cloud.
  3. Create an Organisation (org) — all products are provisioned per org.

Base URLs and environmentslink

HostServesCollection variable
https://api.newinstance.cloudREST API — every request in this collection unless stated otherwise{{baseUrl}}
https://service.newinstance.cloudMCP agent endpoint (AI Agent Access){{serviceUrl}}
https://widget.newinstance.cloudChat widget embed script (Chat)

There is no separate sandbox host. Test safely against the same production URL with a test-mode key (sk_test_…): test and live keys are stored in physically separate collections server-side, so test-key traffic can never read or write live data. Switch to a sk_live_… key when you go to production — see Go-Live Checklist.

The environment variable in this collection is a data label you attach to events (production / staging / development) and the Secret Manager environment selector — it does not change which host you call.


Generate a central API keylink

API keys are created at Dashboard → Org → API Keys (/dashboard/org/[orgId]/api-keys).

Key format: sk_test_<keyId>:<secret> (test) or sk_live_<keyId>:<secret> (live)

The full keyId:secret string is shown once — copy it immediately.

Security rule: The keyId:secret form is for server-to-server calls only. Never embed it in browser code, mobile apps, or client-side scripts.


Permission scopeslink

When creating a key you choose which product(s) and permission groups it covers. Each product has its own scope codes:

BugWatch scopes

Scope codeWhat it grants
ingest:writeSend events — server ingest, browser-session mint, browser ingest, mobile ingest, OTLP, Prometheus, RUM
deploy:writeReport CI deployments, stage transitions and deploy logs (Deployments)
symbols:uploadUpload R8/ProGuard/dSYM/source-map artifacts at build time
symbols:readList and poll debug symbol uploads
symbols:reprocessRe-symbolicate crashes after uploading late symbols
symbols:deleteDelete symbol uploads
error-ingestion / log-access / analytics-access / read-onlyDashboard-style read/ingest splits for reporting keys
ingestLegacy code — grants full BugWatch access (kept for old keys; prefer the granular codes)
full-access / bugwatch-adminAll BugWatch permissions

Support Tickets scopes

Scope codeWhat it grants
full-accessAll support-ticket permissions (recommended)
ticket-managementCreate, read, update, assign, close tickets
ticket-configurationRead/write ticket configuration
read-onlyRead tickets and config only

Secret Manager scopes

Scope codeWhat it grants
full-access / secret-adminAll secret-manager permissions
secret-readFetch MEK and encrypted variables (what your runtime needs)
secret-writeCreate/update encrypted variables
secret-rotationRead/write rotation state
read-onlySecret metadata only (no values)

Chat scopes (widget key — keyId only, no secret)

Scope codeWhat it grants
full-accessAll chat permissions
ai-chatbot-accessInteract with the AI chatbot
ai-chatbot-configurationConfigure/train the AI chatbot
live-chat-operationsManage live chat sessions
chat-configurationConfigure widget settings
read-onlyRead chats and config only

Docs Portal scopes

Scope codeWhat it grants
full-accessAll docs-portal permissions
content-managementCreate / edit / delete pages and sections
publish-managementPublish / unpublish portals and pages
api-reference-managementImport and manage OpenAPI specs
portal-configurationBranding, theming, layout, SEO
domain-managementManage custom domains and DNS
read-onlyRead-only access

The authentication schemeslink

SchemeHeaderUsed by
Central API keyx-api-key: sk_live_KEYID:secretServer-side calls for all products, including the MCP agent endpoint. Authorization: Bearer KEYID:secret is also accepted on BugWatch ingest, OTLP and MCP.
Widget key (publishable)x-api-key: sk_live_KEYID (keyId only, no secret)Chat widget + chat mobile SDKs — safe to ship in client code; server-side it is clamped to chat operations only
Browser session tokenx-bugwatch-session: <token>BugWatch browser ingest + RUM — minted server-side (1 h TTL), used client-side
Mobile tokenx-bugwatch-token: <token>BugWatch mobile SDK — HMAC-signed on device (5 min expiry), never the secret

Environment variableslink

VariableDescriptionSecret?
baseUrlREST API base URL — https://api.newinstance.cloudNo
serviceUrlMCP agent endpoint host — https://service.newinstance.cloudNo
apiKeysk_test_KEYID:secret or sk_live_KEYID:secret — copy from dashboardYES
projectIdBugWatch project public IDNo
mobileAppSecretPer-project mobile HMAC secretYES
appIdSecret Manager app IDNo
environmentEvent environment label (production/staging/development)No
releaseApp release version e.g. 2.1.0No
sessionTokenAuto-filled by "Mint browser session"No
uploadIdAuto-filled by symbol presign requestsNo
deployIdAuto-filled by "Start deployment"No
ticketIdAuto-filled by "Create ticket"No
GET/api/auth/verify

Verify API key

Verify that your API key is valid and inspect its metadata.

Run this first after generating a key to confirm it is active and check the environment (test vs live).

Authentication

  • Header: x-api-key: {{apiKey}}

Success — 200 OK

{
  "success": true,
  "message": "API key is valid",
  "business": { "id": "org_abc123", "name": "Acme Corp", "slug": "acme-corp" },
  "key": { "id": "sk_test_abc123", "environment": "test" },
  "timestamp": "2026-06-26T10:00:00.000Z"
}

Common errors

  • 401 — key missing, malformed, or revoked
  • 403 — key found but inactive

Headers

x-api-key

Responses

200 – Key valid

{
  "success": true,
  "message": "API key is valid",
  "business": {
    "id": "org_abc123",
    "name": "Acme Corp",
    "slug": "acme-corp"
  },
  "key": {
    "id": "sk_test_abc123",
    "environment": "test"
  },
  "timestamp": "2026-06-26T10:00:00.000Z"
}
boltTry it
env
GEThttps://api.newinstance.cloud/api/auth/verify

Headers

x-api-key

Code samples

curl -X GET 'https://api.newinstance.cloud/api/auth/verify'