Hi
Following the documentation for the API, I have been attempting to build a connector within the Microsoft PowerApps environment for use with Power Automate (Flow).
I have not had much success and was wondering if anyone had been successful in building a connector for SMS.
My intention is to integrate into Sharepoint 365 for notifications and acknowledgements similar to the Nexmo connector which I was successful in testing, however I would prefer to use the AT&T API as costings fall under our AT&T account.
Thanks for any assistance.
Thanks for contributing to the AT&T API Marketplace Developer Community!
Great question, will engage some experts to address your question. Stay tuned!
Thanks for replying.
Here’s the swagger editor code that I have managed to generate using the Custom Connector builder in the PowerApps environment. I have next to no web API experience and have no colleagues in the company who can assist as we outsource most development.
Cheers.
swagger: '2.0'
info: {title: ATTConnector, description: ATT Connector for SMS and Calls, version: '1.0'}
host: oauth-cpaas.att.com
basePath: /cpaas
schemes: [https]
consumes: []
produces: []
paths:
/smsmessaging/v1/{userId}/outbound/{senderAddress}/requests:
post:
responses:
default:
description: default
schema:
type: object
properties:
outboundSMSMessageRequest:
type: object
properties:
address:
type: array
items: {type: string}
description: address
clientCorrelator: {type: string, description: clientCorrelator}
deliveryInfoList:
type: object
properties:
deliveryInfo:
type: array
items:
type: object
properties:
address: {type: string, description: address}
deliveryStatus: {type: string, description: deliveryStatus}
description: deliveryInfo
resourceURL: {type: string, description: resourceURL}
description: deliveryInfoList
outboundSMSTextMessage:
type: object
properties:
message: {type: string, description: message}
description: outboundSMSTextMessage
resourceURL: {type: string, description: resourceURL}
senderAddress: {type: string, description: senderAddress}
description: outboundSMSMessageRequest
summary: Send SMS
description: Send SMS
operationId: SendSMS
parameters:
- {name: userId, in: path, required: true, type: string}
- {name: senderAddress, in: path, required: true, type: string}
- name: body
in: body
required: false
schema:
type: object
properties:
outboundSMSMessageRequest:
type: object
properties:
address:
type: array
items: {type: string}
description: address
clientCorrelator: {type: string, description: clientCorrelator}
outboundSMSTextMessage:
type: object
properties:
message: {type: string, description: message}
description: outboundSMSTextMessage
description: outboundSMSMessageRequest
/auth/v1/token:
post:
responses:
default:
description: default
schema:
type: object
properties:
access_token: {type: string, description: access_token}
expires_in: {type: integer, format: int32, description: expires_in}
refresh_expires_in: {type: integer, format: int32, description: refresh_expires_in}
refresh_token: {type: string, description: refresh_token}
token_type: {type: string, description: token_type}
id_token: {type: string, description: id_token}
not-before-policy: {type: integer, format: int32, description: not-before-policy}
session_state: {type: string, description: session_state}
scope: {type: string, description: scope}
summary: Get token
operationId: GetToken
description: Get token
parameters:
- name: body
in: body
required: false
schema: {type: string}
x-ms-visibility: internal
/auth/v1/userinfo:
get:
responses:
default:
description: default
schema:
type: object
properties:
sub: {type: string, description: sub}
preferred_username: {type: string, description: preferred_username}
email: {type: string, description: email}
name: {type: string, description: name}
given_name: {type: string, description: given_name}
family_name: {type: string, description: family_name}
services-identity: {type: string, description: services-identity}
sms-did-list: {type: string, description: sms-did-list}
call-did-list: {type: string, description: call-did-list}
summary: Get user info
description: Get user info
operationId: GetUserInfo
parameters: []
x-ms-visibility: internal
/auth/v1/{userId}/codes:
post:
responses:
default:
description: default
schema:
type: object
properties:
code:
type: object
properties:
resourceURL: {type: string, description: resourceURL}
description: code
summary: Create code
description: Create code
operationId: CreateCode
parameters:
- {name: userId, in: path, required: true, type: string}
- name: body
in: body
required: false
schema:
type: object
properties:
2faCode:
type: object
properties:
address:
type: array
items: {type: string}
description: address
method: {type: string, description: method}
format:
type: object
properties:
length: {type: integer, format: int32, description: length}
type: {type: string, description: type}
description: format
expiry: {type: integer, format: int32, description: expiry}
message: {type: string, description: message}
description: 2faCode
x-ms-visibility: internal
/auth/v1/{userId}/codes/{codeId}:
delete:
responses:
default:
description: default
schema:
type: object
properties:
code:
type: object
properties:
resourceURL: {type: string, description: resourceURL}
description: code
summary: Delete Code
description: Delete Code
operationId: DeleteCode
parameters:
- {name: userId, in: path, required: true, type: string}
- {name: codeId, in: path, required: true, type: string}
- name: body
in: body
required: false
schema:
type: object
properties:
2faCode:
type: object
properties:
address:
type: array
items: {type: string}
description: address
method: {type: string, description: method}
format:
type: object
properties:
length: {type: integer, format: int32, description: length}
type: {type: string, description: type}
description: format
expiry: {type: integer, format: int32, description: expiry}
message: {type: string, description: message}
description: 2faCode
x-ms-visibility: internal
put:
responses:
default:
description: default
schema:
type: object
properties:
code:
type: object
properties:
resourceURL: {type: string, description: resourceURL}
description: code
summary: Update code
description: Update code
operationId: UpdateCode
parameters:
- {name: userId, in: path, required: true, type: string}
- {name: codeId, in: path, required: true, type: string}
- name: body
in: body
required: false
schema:
type: object
properties:
2faCode:
type: object
properties:
address:
type: array
items: {type: string}
description: address
method: {type: string, description: method}
format:
type: object
properties:
length: {type: integer, format: int32, description: length}
type: {type: string, description: type}
description: format
expiry: {type: integer, format: int32, description: expiry}
message: {type: string, description: message}
description: 2faCode
x-ms-visibility: internal
/auth/v1/{userId}/codes/{codeId}/verify:
put:
responses:
default:
description: default
schema:
type: object
properties:
code:
type: object
properties:
resourceURL: {type: string, description: resourceURL}
description: code
summary: Verify Code
description: Verify Code
operationId: VerifyCode
parameters:
- {name: userId, in: path, required: true, type: string}
- {name: codeId, in: path, required: true, type: string}
- name: body
in: body
required: false
schema:
type: object
properties:
code:
type: object
properties:
verify: {type: string, description: verify}
description: code
x-ms-visibility: internal
definitions: {}
parameters: {}
responses: {}
securityDefinitions:
basic_auth: {type: basic}
security:
- basic_auth: []
tags: []reply received from AT&T
From: Marketplace marketplace@att.com
Sent: Friday, December 11, 2020 11:11
To: Byrn, Michael
Subject: RE: Support ticket - official connector for the Microsoft PowerApps/PowerAutomate ecosystem
Michael,
Thank you for contacting AT&T. Unfortunately, this is not on our Roadmap yet.
If anything changes, we will let you know.
Thank you for choosing AT&T.
Hi, AT&T Market place support sending and receiving SMS, you can check https://apimarket.att.com/developer/quickstarts/rest-api/sms-messaging
Unfortunately, We do not provide connectors for PowerApps environment