If you haven't already, become a member of the AT&T Developer Program. Then, sign-in and go to the AT&T API Platform page. Click the Upgrade to Full Access button to get started.
If you are the Administrator for an Organization, you'll create an Organization Profile, in which you'll tell us about your Organization. You'll need to designate yourself as the Organization Profile Administrator, who has the authority to sign Legal Agreements, and who will manage the users who are associated with the Organization.
You'll also be able to set up a Merchant Account (which we'll use to pay you, if you use the Payment API). Here's a list of the key information you'll need to know during registration of a Merchant Account:
If you are a person who wants to be associated with an existing Organization, you'll be shown how to contact the Administrator to get access. Once you've joined an existing Organization and that Administrator has purchased access to the AT&T API Platform, all members of the Organization will have access.
The Sandbox realm provides a lower throughput level, a lower maximum number of transactions allowed per day and other restrictions. This realm is intended to be a place where developers may safely develop and test their applications as they interact with the network services API. You can learn more about the Sandbox realm in the Getting Started Guide: Sandbox Realm.
NOTE: After an app account has been promoted from the Sandbox realm to the Production realm, the app account will have fewer editable fields in both realms.
An App Key and App Secret are app account credentials that are required to obtain an OAuth access token. Almost all of the RESTful APIs provided by the AT&T API platform require an Oauth access token to be passed in the request for authorization.
For some APIs, the app account credentials are enough to obtain an OAuth access token. However, other APIs require you to obtain user consent authorization in addition to the app account credentials to obtain an OAuth access token.
AT&T has developed sample apps and code snippets for multiple programming languages. The sample app uses the custom library built by AT&T. These libraries (PHP/Ruby/Java) could be reused for the needs of your app or they can also be used as a reference at any time.
AT&T provides a full development ecosystem for the developer in the AT&T API Platform, including the Sandbox, which is a self-service development test environment that aggregates AT&T APIs and supports testing; and the AT&T Application Resource Optimizer (ARO), which allows developers to automatically profile prototype applications to optimize their performance, make battery utilization more efficient, and reduce the network impact.
Applications must always use an OAuth token in the API request header called "Authorization:" in order to consume any of the Network Service APIs. The one exception to this is the Notary Management API which does not require the Authorization security header.
An OAuth access token is obtained by invoking the OAuth API which triggers the authorization process. This process may involve interaction between the application and the API Platform only, as in the case of OAuth Token request, or it may involve interaction between the end-user's browser and the API platform. In the latter case, the secure interaction is initiated by the Developer's application but the secure authentication is intentionally routed around the Developer's application and in so doing assures the end-user that their user credentials are kept secure and are only passed between AT&T and the user's browser. For more details on the difference between OAuth flows involving the user (authorization code type) versus flows not involving the user (client credentials type), compare and contrast the OAuth process descriptions given for "Get Token Request" and "Get User Authorization".
AT&T provides several options to help you get the answers you're looking for quickly:
If you are unable to find the answers you need within the documentation on the API Platform Quick Start Guide page, sign into the AT&T Developer Program website and navigate to the Support section. From there you can review a comprehensive list of FAQs and Tech Tips, search our Community Forums or use our Live Chat service to chat directly with an AT&T technical representative. If you still cannot find the answers you are looking for you can optionally submit a ticket by selecting the Log A Ticket link under the Support tab drop down. AT&T Support will review your issue and quickly take action to troubleshoot and address the issue.
NOTE: If you are not signed into the AT&T Developer Program website, you will not have the option to Log A Ticket.
The payment API is designed to protect the consumer's identifying information. Transactions and subscriptions have a "ConsumerId" value, but that value is a random key that may not be persistent.
No. All notification responses, whether in XML or JSON representation format, will contain the same parameter details. The XML structure may, in some cases, contain additional structures that do not appear in JSON, but this is due to syntax difference between the representation formats and not content or semantic differences in the responses.
Please use the Contact us link to close either your personal AT&T Developer Program membership account or an associated organization account. Refer to the notes below that describe the possible variations with respect to closing your Developer Program account:
Close your Account—Completely close your personal AT&T Developer Program membership account.
If you are the administrator and the only member associated with your organization, then your organization will also be removed. If your organization has multiple members, we will contact you with options.
Close your Organization—Keep your personal membership account, but close an organization for which you are the organization administrator.
All personal membership accounts that are associated with this organization, including yours, will be un-associated from the closed organization. All such membership accounts will be able to participate in the free trial of the AT&T API Platform and continue to enjoy the benefits of being an AT&T Developer Program member.
Leave your Organization—Disassociate your personal membership account from an existing Developer organization.
If you are unsure of whether you are an organization administrator, choose this option. We will contact you if you are an administrator. Once your account has been disassociated, your personal membership account will be able to participate in the free trial of the AT&T API Platform and remain an AT&T Developer Program member.
Transfer Administrator Role—Keep your personal membership account, and give administration and ownership of an organization to someone else.
The Developer Id receiving the organization must have a personal AT&T Developer Program membership account that is not already administrating or associated to a different organization. The person responsible for that Developer Id will also be able to accept administrative responsibility for the organization that is being transferred to the new Id. Please let us know if you also want to disassociate your personal membership account from the organization.
By closing an organization any active subscriptions associated with that organization will also be canceled. Be aware that once you have closed an organization, you will not be able to create a new one with the same name.
If you have questions, contact us and we will be happy to go over your options.
To cancel your API Access yearly subscription, you will need to close or leave the organization it is associated with. You have a few options depending on your role. See the FAQ topic question, How can I close my AT&T Developer Program account for details on closing or leaving your organization.