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
| Product | How it integrates | Where to find it |
|---|---|---|
| BugWatch | REST API + SDKs — error/log ingest, enrichment, OpenTelemetry, symbols, CI deployments | Ingest & Errors, SDK Usage & Event Enrichment, Browser & Mobile, Source Maps & Symbols, OpenTelemetry, Prometheus & Tracing, Deployments (CI/CD), SDK & CLI Directory |
| Support Tickets | REST API — mint sign-in links, create/read tickets + comments; outbound ticket webhooks | Support Tickets, Webhooks |
| Secret Manager | REST API + nism CLI — fetch encrypted secrets at runtime | Secret Manager |
| Chat | Embeddable web widget + native mobile SDKs (Android, iOS, Flutter, React Native) | Chat |
| Docs Portal | Dashboard-managed documentation publishing (OpenAPI/Postman import, custom domains) | Docs Portal |
| AI Agent Access | MCP endpoint — let AI agents query your data with your API key | AI 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
- Sign up at https://www.newinstance.cloud — this creates your account.
- Log in to the merchant dashboard at https://app.newinstance.cloud.
- Create an Organisation (org) — all products are provisioned per org.
Base URLs and environmentslink
| Host | Serves | Collection variable |
|---|---|---|
https://api.newinstance.cloud | REST API — every request in this collection unless stated otherwise | {{baseUrl}} |
https://service.newinstance.cloud | MCP agent endpoint (AI Agent Access) | {{serviceUrl}} |
https://widget.newinstance.cloud | Chat 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:secretform 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 code | What it grants |
|---|---|
ingest:write | Send events — server ingest, browser-session mint, browser ingest, mobile ingest, OTLP, Prometheus, RUM |
deploy:write | Report CI deployments, stage transitions and deploy logs (Deployments) |
symbols:upload | Upload R8/ProGuard/dSYM/source-map artifacts at build time |
symbols:read | List and poll debug symbol uploads |
symbols:reprocess | Re-symbolicate crashes after uploading late symbols |
symbols:delete | Delete symbol uploads |
error-ingestion / log-access / analytics-access / read-only | Dashboard-style read/ingest splits for reporting keys |
ingest | Legacy code — grants full BugWatch access (kept for old keys; prefer the granular codes) |
full-access / bugwatch-admin | All BugWatch permissions |
Support Tickets scopes
| Scope code | What it grants |
|---|---|
full-access | All support-ticket permissions (recommended) |
ticket-management | Create, read, update, assign, close tickets |
ticket-configuration | Read/write ticket configuration |
read-only | Read tickets and config only |
Secret Manager scopes
| Scope code | What it grants |
|---|---|
full-access / secret-admin | All secret-manager permissions |
secret-read | Fetch MEK and encrypted variables (what your runtime needs) |
secret-write | Create/update encrypted variables |
secret-rotation | Read/write rotation state |
read-only | Secret metadata only (no values) |
Chat scopes (widget key — keyId only, no secret)
| Scope code | What it grants |
|---|---|
full-access | All chat permissions |
ai-chatbot-access | Interact with the AI chatbot |
ai-chatbot-configuration | Configure/train the AI chatbot |
live-chat-operations | Manage live chat sessions |
chat-configuration | Configure widget settings |
read-only | Read chats and config only |
Docs Portal scopes
| Scope code | What it grants |
|---|---|
full-access | All docs-portal permissions |
content-management | Create / edit / delete pages and sections |
publish-management | Publish / unpublish portals and pages |
api-reference-management | Import and manage OpenAPI specs |
portal-configuration | Branding, theming, layout, SEO |
domain-management | Manage custom domains and DNS |
read-only | Read-only access |
The authentication schemeslink
| Scheme | Header | Used by |
|---|---|---|
| Central API key | x-api-key: sk_live_KEYID:secret | Server-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 token | x-bugwatch-session: <token> | BugWatch browser ingest + RUM — minted server-side (1 h TTL), used client-side |
| Mobile token | x-bugwatch-token: <token> | BugWatch mobile SDK — HMAC-signed on device (5 min expiry), never the secret |
Environment variableslink
| Variable | Description | Secret? |
|---|---|---|
baseUrl | REST API base URL — https://api.newinstance.cloud | No |
serviceUrl | MCP agent endpoint host — https://service.newinstance.cloud | No |
apiKey | sk_test_KEYID:secret or sk_live_KEYID:secret — copy from dashboard | YES |
projectId | BugWatch project public ID | No |
mobileAppSecret | Per-project mobile HMAC secret | YES |
appId | Secret Manager app ID | No |
environment | Event environment label (production/staging/development) | No |
release | App release version e.g. 2.1.0 | No |
sessionToken | Auto-filled by "Mint browser session" | No |
uploadId | Auto-filled by symbol presign requests | No |
deployId | Auto-filled by "Start deployment" | No |
ticketId | Auto-filled by "Create ticket" | No |
/api/auth/verifyVerify 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 revoked403— key found but inactive
Headers
x-api-keyResponses
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"
}https://api.newinstance.cloud/api/auth/verifyHeaders
x-api-keyCode samples
curl -X GET 'https://api.newinstance.cloud/api/auth/verify'