No, the user consent changes only impact the user. Developers with active apps do not need to make any changes.

User consent authorization is the process by which a user authorizes, or provides consent for, specific APIs provided by AT&T to be used with the user's customer account or mobile device.

Apps present users with a set of secure Web-based interactions prior to the app requesting access to certain APIs. Today the In-App Messaging API is the only API that requires user consent. User consent authorization is neither required nor available for the other APIs.

For more information about supporting user consent authorization, see the API Documentation page for the API in which you are interested. Source code and examples are provided.

There are no API changes that will cause a developer to change their code or apps.

Developers and users will see updated graphics on the user consent verification screens. In addition, there is a change in the way that users provide consent via SMS messages. Starting with API Platform release 3.0, rather than requesting for the user's mobile number and sending a PIN, the user consent pages will display a word code and allow the user to send the code from their AT&T Wireless mobile device to provide consent which eliminates an extra step.

The easiest way to see the updates is to run the sample apps or sign in to My Apps. The Sample Apps are found in the documentation for each API. Choosing a Web-based interface like RESTful Java allows you to display an example in your Web browser window. Just choose a Sample App that uses the Payment API or In-app Messaging API and run through the Sample App to see the user consent updates. Alternatively, click on the Authorize button on the top-right of My Apps to see the user consent flow in action.

To get a good feel for the experience, access the Sample App using both a desktop and mobile browser.