New to SMS API need guidance

Trying to get a grip on a potential idea for SMS (receiving only from AT&T numbers). I signed up for ATT Developer API and reviewed their Terms; states unlimited incoming SMS (we are estimating 3.5M per month from various numbers). Is the developer side only for development purposes because the FREE ACCESS terms state differently. Almost like you can run an in-production API link indefinitely? This idea would have to be a standalone APP running on a city owned computer with a Short Code owned by the city. Can the city apply for an ATT Developer Account and utilize the free access?

I found that even with the free account stating incoming was included, the ability to Authenticate the API appeared to hinge on having a paid account (or one attached to an existing AT&T business account). Regardless you will probably need to raise this with the Marketplace support.

Hi @mbyrntcm - are you referring to SMS APIs at AT&T SMS API | AT&T Developer or https://apimarket.att.com/developer/references/rest-api/1.0.0#sms ?

Meron:

That is what I am looking to get clarified from ATT; when to use which service (Developer vs. Marketplace). I want to develop an application that will reside on a customer computer , each sale of the application will require an individual short code acquired directly by the customer. If we give the application to that customer can they just apply for the developer Free Access and acquire the short code themselves at no charge. Our application will only receive SMS no outgoing messaging.

Thanks,

Douglas Schafer

Hydraservice

Michael:

Thank you for the response. I posed my question to every department within ATT to get clarification from Marketplace to Legal. I cannot get a clear answer. Before I start development I need to understand the proper channel to start, costs to customer for service, and legal constraints to getting a short code and access. Can you point me in a direction within ATT? I literally have over 100 email strings from different departments with conflicting or unclear answers.

Thank you,

Douglas Schafer

Hydraservice, Inc.

Yes. I tried to use the API spec to write my own custom connector in the PowerApps environment that I could share with my colleagues internally. I was able to get basic authentication but unable to action any of the functions. I am not a developer and have no experience with cloud-based API integration.

I honestly have no idea. Initially I had some issues with turning my free account into a full account due to the credit check. The person who helped me resolve that was very helpful so I posed this question to him and the silence has been deafening.

Given the size of AT&T vs a company like Nexmo (now owned by Vonage) I expect change and development doesn’t come swiftly and this level of cross-platform integration is probably a brave new frontier vs the old stacked cellular modem back with multiple SIM cards plugged into the application server. However they are losing the extra percentage to their resellers/VMOs who are more agile at developing these less-than-core functions.

I have also signed up for the developer portal to see if there is any difference in service offered.

sorry i didn’t fully read. I was trying to use the API marketplace API as my initial use case is for SMS but I would also like to implement recorded voice calling.

The developer API only seems to offer SMS, but I have signed up anyway to see what I can determine.

Whatever you can do to help would be awesome.

Thanks,

Doug

Hi,

As mentioned, the AT&T Marketplace provides easy to use APIs for sending and receiving SMS, you can check https://apimarket.att.com/developer/quickstarts/rest-api/sms-messaging.

We are considering adding a call recording API in a future release.