Sign in
Dialogflow Integration

Create a Dialogflow Connection

Save Dialogflow Credentiails to Telnyx, so it can be used with other Telnyx services.

post/dialogflow_connections/{connection_id}

Path parameters

connection_idstring required

Uniquely identifies a Telnyx application (Call Control).

Request body

service_accountobject required

The JSON map to connect your Dialoglow account.

dialogflow_api'cx' | 'es'

Determine which Dialogflow will be used.

conversation_profile_idstring

The id of a configured conversation profile on your Dialogflow account. (If you use Dialogflow CX, this param is required)

locationstring

The region of your agent is. (If you use Dialogflow CX, this param is required)

environmentstring

Which Dialogflow environment will be used.

Example request

{
  "service_account": {
    "type": "service_account",
    "project_id": "your-project-id",
    "private_key_id": "your-private-key",
    "private_key": "-----BEGIN PRIVATE KEY-----\n-----END PRIVATE KEY-----",
    "client_email": "example@example.com",
    "client_id": "your-client-id",
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token",
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/example%40example.iam.gserviceaccount.com"
  },
  "dialogflow_api": "cx",
  "conversation_profile_id": "a-VMHLWzTmKjiJw5S6O0-w",
  "location": "global",
  "environment": "development"
}

Response

Return details of the Dialogflow connection associated with the given CallControl connection.

Example response

{
  "data": {
    "record_type": "dialogflow_connections",
    "connection_id": "1234541231",
    "conversation_profile_id": "a-VMHLWzTmKjiJw5S6O0-w",
    "environment": "development",
    "service_account": "****"
  }
}

Changes

Changed in 3 of the 99 revisions of this API.6

  • a6a61a29ecdd2See the full diff
    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 1571b0380bd72See the full diff
    • ▲

      the // response's property type changed from integer to string, and format from int32 to no format for status

      response-property-type-changed

    • ▲

      the // response's property type changed from integer to string, and format from int32 to no format for status

      response-property-type-changed

    This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 8f5f4e5379942See the full diff
    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 99 revisions, 1 has no diff computed.