Support Channels & Diagnostic Telemetry
When you need engineering assistance, onboarding guidance, or incident triage, reaching out with structured diagnostic identifiers allows the Passinstance support team to trace your exact API request, background job, or wallet callback immediately.
-
Direct Support Desk: support@passinstance.com
-
Web Intake Form: Contact Passinstance
-
Guided Pilot & Nonprofit Intake: Request a Pilot
-
Product Changelog: Release Notes
Required Diagnostic Identifiers for Fast Resolution
Include the following identifiers (when applicable) in your support ticket so engineers can correlate logs without back-and-forth delays:
| Diagnostic Identifier | Example Format | Where to Find It |
|---|---|---|
Request Correlation ID (requestId) | req_8f192b0e4c12 | Returned in every API Error Handler JSON error payload and x-request-id response header. |
Template ID (templateId) & bundleId | 8b3c4d5e-1122-4334-9a8b-7c6d5e4f3a2b | Displayed in the Template Editor URL or returned by GET /api/v1/templates (bundleId = Apple passTypeIdentifier). |
Pass Serial / externalId | PASS-2026-99412 | Shown on the back of the wallet pass, in the Passes table, or in passSnapshot in the scan response. |
Webhook ID (webhookId) | wh_55a9c102e4b1 | Sent in the X-Webhook-Id HTTP header on outbound push webhooks or queried via GET /webhook-payload. |
| Client OS & Browser | iOS 18.2 Safari / Android 15 Chrome | Helpful when diagnosing passholder download or wallet installation issues. |
Important: Never send raw API keys (
pi_live_...), scanner keys, account passwords, or Apple.p12certificate passwords in support emails or tickets. Passinstance engineers never require your secret keys to inspect your workspace.
Public Contact & Operational Health Endpoints
Integrators and monitoring systems interact with Support Intake API (/api/v1/contact*) and prefix-free Health Check API (/health*):
| Endpoint Path | Method | Auth | Description |
|---|---|---|---|
/api/v1/contact | POST | Public | Submits a structured support or sales inquiry (name, email, company, message). |
/api/v1/contact/subscribe | POST | Public | Subscribes an email address to platform release and operational announcements. |
/health | GET | Public | Standard health check verifying core database and in-memory cache readiness. |
/health/liveness | GET | Public | Lightweight container liveness probe confirming HTTP server responsiveness. |
/health/readiness | GET | Public | Verifies database pool and cache readiness before accepting ingress traffic. |
/health/detailed | GET | Bearer / Ops | Returns granular subsystem status across Database, in-memory cache, Google Wallet API, background job queues, Mailer, and webhook Circuit Breakers. |
Example: Inspecting Detailed Subsystem Health (GET /health/detailed)
{
"status": "ok",
"timestamp": "2026-11-15T22:30:00.000Z",
"components": {
"database": { "status": "up", "latencyMs": 3 },
"cache": { "status": "up", "latencyMs": 1 },
"googleWalletApi": { "status": "up" },
"jobQueue": { "status": "up", "activeJobs": 4 },
"mailer": { "status": "up" },
"circuitBreakers": { "openWebhooks": 0 }
}
}
Submitting a Support Inquiry via API (POST /api/v1/contact)
{
"name": "Marcus Vance",
"email": "marcus@retailops.example.com",
"company": "Vance Retail Group",
"message": "Investigating webhook circuit breaker cooldown on webhookId wh_55a9c102e4b1 (requestId: req_8f192b0e4c12)."
}
For immediate self-service diagnostics, check Troubleshooting & FAQs and Known Issues & Limitations.
