Opentact
  • Opentact Introduction
  • KEY CONCEPTS
    • Basic Concept
      • Voice Capability
        • Managing Inbound Calls
      • SMS Capability
      • Number Capability
    • Phone Number
      • Voice Enablement
      • SMS Enablement
      • TN Profile
        • Blacklist Caller ID
        • Whitelist Caller ID
    • SIP Control APP
      • Specify Remote Call Control URL
      • Specify Dialplan XML
    • SIP Trunking
    • Messaging
      • Quick Start Guide
      • Prepare Phone Numbers for SMS
    • SIP Connection
      • Associate SIP Connection with Phone Number
    • SIP Domain
      • Send Outbound Call with SIP Domain
      • Receive Inbound Call to SIP User
        • Web Call
        • Zoiper SIP Client
    • SIP Users
      • Create a SIPUser
      • Create a SIPUserInvite
    • Telecom Data
  • Opentact API Documentation
    • Opentact API Integration
      • API Environment
      • Opentact API keys
      • Passing Authentication
      • Authentication API
        • Example API Call
        • Authentiction with Gmail
    • TN Profile
      • Add and Remove Blacklist to TN Profile
        • Example API Call
      • Add and Remove Whitelist to TN Profile
        • Example API Call
    • Phone Number
      • Order Phone Number
        • Example API Usage
      • Release a Number
        • Example API Usage
      • Get all Purchased Numbers
      • Number Search
        • Example API Usage
    • SIP Connection
      • Remove Number from SIP Connection
      • Get Number for a SIP Connection
      • Update SIP Connections
      • Create SIP Conenctions
      • Delete SIP Connections
      • List SIP Connections
      • Assign Number to a SIP Connection
    • Messaging
      • Enable SMS on Numbers
      • Disable SMS on Number
      • Send SMS with Pool
      • Send SMS with Number
      • Receiving SMS
      • Retrieve Message Detail Records
      • Receiving Messaging Events
    • Log Retrieval
      • Retrieve Call Log
      • Retrieve SMS Log
    • Calling
      • Bridge two calls
      • Make Single Call
      • Make Bulk Call
        • Example API Call
    • SIP Domain
      • Create SIP Domain
      • Create SIP User
      • Deleting SIP User
      • Modify SIP User
    • Websocket Event Subscription
      • Create Subscription
      • Remove Subscription
      • Get Subscribed Events
        • Example API Call
  • Websocket Events
    • Event Websocket
    • Websocket Authentication
      • How to Authenticate to WSS
      • Authentication Response
      • Explanation of JSON response
    • Event Definition
      • Call Initiated
        • Example Event
      • Call Ringing
        • Example Event
      • Call Live
        • Example Event
      • Callflow
        • Example Event
      • Call Hangup
        • Example Event
      • Call Destroyed
        • Example Event
      • Call Bridged
        • Example Event
      • Call Answered
        • Example Event
      • Account events
        • Example Event
      • SMS events
        • Example Event
      • TN events
        • Example Event
      • Record Events
        • Example Event
      • Transcript
        • Example Event
      • General Event Fields
      • Example Event
  • Opentact XML
    • Overview
    • <Call/>
    • <Callback/>
    • <Geo/>
    • <Scheduler/>
    • <Play/>
    • <Say/>
    • <Hangup/>
    • <Pause/>
    • <Record/>
    • </Dial>
    • </Gather>
    • <Answer/>
    • <Hold/>
    • <Tone/>
    • <Error/>
    • <Default/>
    • <Meta/>
    • <Curl/>
  • How to build your Opentact Application
    • Introduction
    • Inbound Call Control
    • Opentact Events
    • Call Flow Control
      • Specify CallFlow for TN
        • Dynamic Call Flow XML
        • Basic Workflow
      • Handle Inbound Call
    • Send and Receive SMS
      • Life Cycle of SMS Delivery
      • Real-time SMS over Websocket
      • Send SMS via Restful API
    • Send and Receive SIP Calls
      • Create SIP User
      • Make Calls Between SIP User
      • Receive Calls as SIP User
  • Regulatory Compliance
    • 10DLC FAQs
    • Stir Shaken
  • SIP Trunking
    • Use Opentact for SIP Trunking
  • Webhook Event
    • Introduction
    • Test Webhook with Opentact
    • Event Definition
Powered by GitBook
On this page
  • Purpose of the <Curl> Command
  • Key Features
  • Usage Hints
  • Examples
  • Integration Scenarios

Was this helpful?

  1. Opentact XML

<Curl/>

The <Curl> command in Opentact XML call flows empowers users to integrate and interact with external web services seamlessly. This command enables making HTTP requests during a call, allowing dynamic interactions and data exchange with external systems. The <Curl> command is a powerful tool to extend the capabilities of Opentact, making it a versatile solution for various telephony applications.

Purpose of the <Curl> Command

The primary purpose of the <Curl> command is to send HTTP requests to external endpoints, facilitating real-time communication with web servers, APIs, or any HTTP-enabled services. This integration capability enables Opentact users to fetch, push, or manipulate data during a call, enhancing the interactive nature of telephony applications.

Key Features

  • Dynamic Interaction: The <Curl> command allows dynamic interaction with external services based on the context of the call flow.

  • Data Exchange: It facilitates the exchange of data between Opentact and external systems, opening up possibilities for personalized and context-aware call experiences.

  • Request Customization: Users can customize HTTP requests by specifying various parameters such as method, headers, body content, and more.

  • Response Handling: Opentact can handle responses from external services, providing the flexibility to make decisions based on the received data.

Usage Hints

  • URL Configuration: The url parameter specifies the endpoint to which the HTTP request is made.

  • Request Method: Users can define the HTTP method (GET, POST, etc.) using the method parameter.

  • Timeout: The timeout parameter sets the maximum time allowed for the HTTP request.

  • Response Handling: Users can decide how to handle the HTTP response, whether to include it in the call flow or simply acknowledge the request.

Examples

Here are some examples illustrating the usage of the <Curl> command in Opentact XML call flows:

<Curl url="https://api.example.com/data" method="GET" timeout="5000" />
<Curl url="https://api.example.com/update" method="POST" body="{'key':'value'}" />

Integration Scenarios

  • Data Retrieval: Fetch information from external databases or APIs to provide real-time updates during a call.

  • Service Integration: Integrate Opentact with third-party services to perform actions based on call events.

  • Customization: Dynamically customize call flows by fetching data from external sources.

The <Curl> command adds a layer of sophistication to Opentact call flows, allowing users to seamlessly integrate telephony processes with external services.

Previous<Meta/>NextIntroduction

Last updated 1 year ago

Was this helpful?