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
  • Templates
  • 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.

PrivacyTermsEmail support

Need a hand?

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

Open developer support
  1. Docs
  3. Test in the sandbox

Developer workflow

No code required

Test in the sandbox

Compose requests against the real partner API, inspect the exact payload and response, and graduate selected scenarios to controlled live delivery on your own test accounts.

Two test modes, different safety boundaries

Dry-run
Validates through the API without delivering. This is the default and works with arbitrary example recipients.
Live test delivery
Delivers WhatsApp text, templates and media, and Instagram text and media, only to the numbers and Instagram accounts you registered as test recipients.
Recommended first

Validate with a dry-run

Select a connected client, channel, message type, and scenario. The sandbox builds the same JSON your code will send and shows both the outgoing request and parsed response.

A dry-run checks

  • Bearer-key authentication and required scopes
  • client_ref lookup and channel routing
  • Request shape and message-type validation
  • Channel capability checks
  • Normalized success or error response

Test keys deliver only to your test recipients

An ik_test_ key can never reach a real end-customer: every send is simulated unless to is one of your registered test recipients — your own WhatsApp number or Instagram username — which receives the real message. That makes the same test key safe in local, preview, and CI environments, while still letting you verify delivery end-to-end on your own device. An explicit dry_run: true always simulates.

Send to a registered test recipient

Live testing is intentionally narrower than the production API. It requires the portal's global mode to be Live, a connected client, and a registered test recipient for the channel — your own WhatsApp numbers or Instagram usernames, up to two per channel. The same recipients gate real deliveries from ik_test_ keys.

Live sandbox coverage

Controlled live delivery covers WhatsApp text, templates and media, and Instagram text and media. For Instagram, to is the Instagram-scoped ID of your test account — take it from the webhook you receive after messaging the connected account; Intelli resolves it to the username you registered before delivering. Interactive payloads, reactions, location and contacts stay dry-run in the sandbox; the API carries them, so exercise those from your own code.

Recommended workflow

  1. 1. Start from a scenario. Pick the closest message type and adjust only the fields your integration controls.
  2. 2. Run dry. Resolve validation, scope, client, and channel errors before attempting delivery.
  3. 3. Copy the request. Move the successful headers and body into an automated integration test.
  4. 4. Deliver narrowly. Register your own phone as a test recipient and exercise one live text or template.
  5. 5. Trace the call. Confirm the request ID, request log, and webhook delivery before a broader rollout.
Ready to exercise the API?

The sandbox uses your partner account, keys, connected clients, and test recipients, so you need to sign in.

Open API Sandbox
PreviousQuickstart
NextAuthentication