Getting Started

Getting Started with New Instancelink

New Instance is a multi-product developer platform: one account, one organisation, one API key model - and a suite of products you can adopt independently:

• BugWatch - error monitoring, logs, traces, metrics and release health, with SDKs for server, browser and mobile.
• Support Tickets - a hosted customer-support portal plus a REST API to create and read tickets on your customers' behalf.
• Secret Manager - end-to-end-encrypted configuration your apps fetch at runtime; the platform stores only ciphertext.
• Chat - an embeddable live-chat + AI chatbot widget for the web, with native mobile SDKs.
• Docs Portal - publish branded documentation for your product, with an interactive API reference (this very site is built with it).
• AI Agent Access - an MCP endpoint that lets AI agents query your data with your own API key.

Everything is provisioned per organisation: you create an org, enable products, create API keys scoped to those products, and every credential, project and portal lives under that org. This page walks that path - account, organisation, keys, scopes, authentication schemes - and every product section assumes you've done it.

---

Productslink

Cross-cutting references: Webhooks - Receiving Platform Events and Errors, Rate Limits & Troubleshooting.

---

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

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 keyspaces server-side, so test-key traffic can never read or write live data. Switch to a sk_live_… key when you go to production.

The environment value used throughout this reference 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

Support Tickets scopes

Secret Manager scopes

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

Docs Portal scopes

Docs Portal authoring is dashboard-driven today: these scopes govern keys used by platform surfaces, and there is no public REST authoring API (see Docs Portal).

---

The authentication schemeslink

---

Placeholders used in the exampleslink

{
  "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"
}

{
  "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"
}

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