Command Palette

Search for a command to run...

IntelliPortalDOCS

Start here

  • Overview
  • Quickstart
  • Test in the sandbox

Build

  • Authentication
  • Clients
  • Hosted onboarding
  • Webhooks

API reference

  • Messages
  • Usage
  • Status & observability

Reliability

  • WhatsApp limits
  • Errors & debugging

Resources

  • Changelog
  • OpenAPI 3.1
  • Postman collection
Developer support
IntelliPortalDOCS
Developer documentation/API v1

© 2026 Intelli Holdings Inc.

PrivacyContact

Need a hand?

Share a request ID when you contact us so we can trace the call quickly.

Open developer support
  1. Docs
  3. Status & observability

API reference

GET /status

Status & observability

Probe edge availability, carry request IDs through your logs, and use the dashboard to investigate API latency and webhook delivery.

GET/status

Probe the public API edge

This endpoint is unauthenticated and lightweight. Use it to verify DNS, TLS, routing, and the deployed API version.

cURL
curl https://api.intelliconcierge.dev/v1/status
JSON · 200
{
  "status": "ok",
  "version": "v1"
}

Edge health is not a synthetic send

A successful status probe confirms the public edge is reachable. It does not authenticate a key, connect to Meta, or prove a particular client can send. Keep a test-key dry-run in deeper readiness checks.

Correlate with X-Request-Id

Every authenticated public request receives an opaque UUID. Capture it next to your own trace or job ID so one failing send can be followed across systems.

Node.js
const response = await fetch(url, request);
const requestId = response.headers.get("x-request-id");

logger.info("IntelliPortal response", {
  requestId,
  status: response.status,
  clientRef,
});

Request recording runs after the response is sent, so a brand-new request may take a moment to appear in the dashboard.

Investigate from the dashboard

Request Logs

Volume, status distribution, latency percentiles, a latency heatmap, and individual request records.

Open Request Logs
Platform Status

Dashboard health view for the partner API and its supporting services.

Open Platform Status
Webhook Deliveries

Payload, response status, attempts, failure context, and manual redelivery.

Open Webhook Deliveries

Production monitoring checklist

  • Alert on sustained 5xx or 502 upstream_unavailable, not a single transient response.
  • Track 429 separately and honor Retry-After before retrying.
  • Treat webhook failures as a separate signal from outbound API failures.
  • Log client_ref and X-Request-Id, but never a full API key or webhook signing secret.
  • Include the request ID, timestamp, endpoint, and HTTP status in a developer support ticket.
PreviousUsage
NextWhatsApp limits