IssueTracker

// Note: This will create a feature request which anybody can view and comment on.

-- Requested enhancement description (What would you like to accomplish?) --

Clients would like the ability to enable the Dialogflow messenger Integration (or Integrations in general) for Dialogflow agents programmatically (Client Library, REST)instead of using the console.[1]

Chief request is to make the  “google.cloud.dialogflow.v3alpha1.Integrations.StartIntegration” Publicly available

-- Detailed functionality description (How might it work? What needs to be changed?) --

- Expected behavior

200 response when sending POST request to “google.cloud.dialogflow.v3alpha1.Integrations.StartIntegration” API

- Actual behavior
`
curl -X POST 'https://dialogflow.clients6.google.com/v3alpha1/projects/[REDACTED]/locations/global/agents/[REDACTED]/integrations:start?alt=json' \

 -H 'Authorization: Bearer ya29.xxxx-xxx-xxx--xxxxx-2hQ0181' \

 -H 'content-type: application/json' \

 -H 'origin: https://dialogflow.cloud.google.com' \

 -H 'x-goog-user-project: [REDACTED] \

 --data-raw '{"integration":{"dialogflowMessengerPayload":{"allowedDomains":[],"isAuthenticated":false},"environment":"","type":"DIALOGFLOW_MESSENGER"}}'

{

 "error": {

  "code": 404,

  "message": "Method not found.",

  "status": "NOT_FOUND"

 }

}
`


-- If applicable, reasons why alternative solutions are not sufficient --

Note it is possible to enable the Dialogflow Messenger API authenticating using the SAPISIDHASH and cookies generated by the console request[1], but not with an access token or scoped credentials

-- Steps to reproduce the issue (detailed description)  --

1. Enable the Dialogflow Messenger Integration as per our public doc[1]

2. Copy the integration:start request as acURL from the network tag of the chrome develope console following the instructions from this related public issue tracker[2]

3. Disable the Dialogflow Messenger Integration in the console

4. Run cURL request in a gcloud authorized shell

5. Observe it possible authenticating using the authorization SAPISIDHASH and cookies generated by the console request

6. Attempt this same cURL request using a generated access token or ADC, then either a '401' Permission Denied or '404' METHOD_NOT_FOUND response generated

-- Other information (workarounds you have tried, documentation consulted, etc) --

[1]: https://cloud.google.com/dialogflow/cx/docs/concept/integration/dialogflow-messenger
[2]: https://issuetracker.google.com/220673205#comment11