Environments

Production API URL, mc_live vs mc_test keys, and staging.

Base URLs

Environment	API base URL	Dashboard
Production	`https://api.mailingcore.com`	`https://app.mailingcore.com`
Local dev	`http://localhost:3010`	`http://localhost:5173`
Staging	Available on request	Same dashboard with test data

OpenAPI interactive docs: https://api.mailingcore.com/docs · JSON spec: /docs-json.

API key prefixes

Prefix	Purpose
`mc_live_`	Production sends — counts against quota, delivers via SES
`mc_test_`	Sandbox / development — safe for CI and browser tests

SDK configuration

MailingCore.init({
  apiKey: process.env.MAILINGCORE_API_KEY!, // mc_live_ or mc_test_
  baseUrl: 'https://api.mailingcore.com',
})

Headers

Header	When required
`Authorization: Bearer <key or JWT>`	Always
`X-Tenant-Id: <tenantId>`	JWT dashboard calls; optional with API key (tenant resolved from key)
`Content-Type: application/json`	POST/PATCH bodies

Staging notes

Staging mirrors production architecture with separate credentials and data. Use mc_test_ keys for integration work before going live. See FAQ for maturity notes.

Authentication — JWT vs API key
Multi-tenant — X-Tenant-Id rules
Init and configuration