Dialpad

Place calls and pull call/SMS records for sales reps via the Dialpad REST API.

This InTouch tool wraps four core Dialpad operations so you can pull a rep's call history into a job, look up a specific call, send an SMS follow-up, or kick off an outbound call — all without writing any HTTP plumbing.

Base URL: https://dialpad.com (Dialpad also offers https://sandbox.dialpad.com)
Auth: Authorization: Bearer <apiKey> — a static API key, no OAuth exchange needed.

Operations

operation	method & path	what it does
`list-calls`	`GET /api/v2/call`	Paginated, reverse-chronological list of concluded calls. Filter by time range and target. (Needs a company-admin key with the `calls:list` scope.)
`get-call`	`GET /api/v2/call/{callId}`	Detailed info for one concluded call: direction, duration, recording URLs, routing, voicemail, transcript text.
`send-sms`	`POST /api/v2/sms`	Send an SMS to one or more E.164 numbers.
`place-call`	`POST /api/v2/users/{userId}/initiate_call`	Ring a user's device and place an outbound call to a destination number.

API key setup

Sign in to the Dialpad admin console.
Go to Company Settings → Authentication → API Keys (a company-admin key is required for list-calls; a user-scoped key is enough for place-call / send-sms).
Create a key and copy it. You can also view your keys at https://developers.dialpad.com ("Log in to see your API keys").
Pass that key as the apiKey input. It is sent as Authorization: Bearer <key>.

Examples

List a rep's recent calls

{
  "apiKey": "your-dialpad-api-key",
  "operation": "list-calls",
  "targetId": "4912345678",
  "targetType": "user",
  "limit": "25"
}

Look up one call

{
  "apiKey": "your-dialpad-api-key",
  "operation": "get-call",
  "callId": "5566778899"
}

Send an SMS follow-up

{
  "apiKey": "your-dialpad-api-key",
  "operation": "send-sms",
  "toNumbers": "+15558675310",
  "text": "Thanks for the call — sending over that proposal now.",
  "userId": "4912345678"
}

Place an outbound call

{
  "apiKey": "your-dialpad-api-key",
  "operation": "place-call",
  "userId": "me",
  "phoneNumber": "+15558675310",
  "outboundCallerId": "+15551112222"
}

Output

Every operation publishes:

result — the raw Dialpad response body as a JSON string.
status — the HTTP status code (e.g. 200).

On error the tool prints {"error": "..."} and exits non-zero, marking the step failed. HTTP 4xx/5xx responses from Dialpad are returned in result with the matching status so you can inspect the error payload.