Skip to main content
Use this guide to run one SMS conversation and one voice-call test against the PAM Outbound API with the reusable PROD_OUTBOUND_XTIME sandbox client. This sandbox is for outbound API prospects and partners who need to test direct SMS, voice, scheduling, and optional webhook behavior before their production client configuration is ready. PAM will provide:
  • API base URL
  • API key for PROD_OUTBOUND_XTIME
  • Allowed fromNumber values for SMS and voice
You will provide:
  • A test recipient phone number
  • An optional HTTPS webhook endpoint, if you want callback events

Setup

Set these values locally:
All phone numbers must use E.164 format. All dynamicVariables values must be strings. For managed PAM agents, include the full vehicle identity:
  • vin
  • vehicle_year
  • vehicle_make
  • vehicle_model
Do not send contact_phone_number. PAM derives the customer’s phone number from toNumber.

Start a test SMS conversation

Create one SMS conversation:
Do not include idempotencyKey for manual SMS smoke tests. Use a fresh externalReferenceId each time. Reusing an idempotency key can return the original conversation instead of creating a new one. Expected result:
  • The API returns 201 Created.
  • The response includes data.conversationId.
  • The test phone receives the opening SMS.
  • If the test recipient replies, the conversation continues on the same thread.
  • If the agent calls scheduling tools, GET /sms-conversations/{conversationId} shows the tool invocation and result messages.
Use the returned conversationId to fetch state:
Close the test conversation when finished:

Start a test voice call

Voice calls require an idempotency key. Use a fresh key for each manual test run. Reuse the same key only when retrying the same request after a network timeout. Create one voice call:
Expected result:
  • The API returns 202 Accepted.
  • conversationId may be null at first. PAM creates it after the call provider accepts the call.
  • The test phone receives a call from PAM_VOICE_FROM_NUMBER.

Optional webhook testing

You do not need to register a webhook for the basic SMS or voice smoke test. If you want callback events, first register a webhook:
The response includes a webhook signing secret once. Store it securely. PAM uses that secret to sign future webhook requests. Confirm the webhook registration:
To send one conversation’s events to a different URL, include webhookUrl in the create request:
The override changes only that conversation’s destination URL. Event subscriptions and signing still come from the registered webhook.

Booking test notes

Booking creates a real appointment in the sandbox scheduler. For manual booking tests, use an internal test contact and close the conversation when finished. The PROD_OUTBOUND_XTIME sandbox lookup may not find the test contact by phone number. Include vin, vehicle_year, vehicle_make, and vehicle_model so the scheduler still has the full vehicle identity.

Troubleshooting