The items on this page represent API Implementations that are supported but no longer actively maintained or enhanced. For newer alternatives, please see below.
Using our current API guarantees that you will always have:
• The latest features
• Continual updates and improvements
• The most active community of fellow developers
Understanding the Authorize.Net API
If you previously integrated with the Authorize.Net platform, you may be used to seeing each of our features documented as separate and distinct APIs. Within our newer documentation, you’ll find that all of our features are a part of a larger cohesive API set.
STATUS: Deprecation Notice
ALTERNATIVE SOLUTIONS: The Authorize.Net API includes all of the SOAP API functionality plus additional features such as Authorize.Net Accept, creating one-time transactions and enhanced Customer Profile methods.
DESCRIPTION: We have deprecated our SOAP API that offered support primarily for Customer Information Manager. We strongly recommend that developers move to the Authorize.Net API using XML or JSON. This will allow us to continue providing developers with the most up-to-date features and to support a single, consistent platform.
STATUS: Deprecated / End-of-Life on March 1, 2018. Upgrade to Accept Customer
DESCRIPTIOn: Hosted CIM has been replaced by Authorize.Net Accept Customer, a fully hosted solution for capturing payment information that allows developers to leverage our Customer Profiles API while maintaining SAQ-A level PCI compliance. Our forms are mobile-optimized and designed to reduce friction in your consumer experience.
Hosted CIM pages at https://test.authorize.net/profile/ are no longer being updated and will return HTTP Error 410 after March 1, 2018.
Server Integration Method (SIM)
ALTERNATIVE SOLUTIONS:SIM is now referred to as Payment Form.
DESCRIPTION: Our hosted payment form and Direct Post Method (DPM) still use our SIM API. You can find everything you need to know about integrating with those features in our Server Integration Method (SIM) Guide (PDF).
Merchant Web Services API (Returns API)
Authorize.Net Reporting API is now the supported method for retrieving eCheck Returns information. http://developer.authorize.net/api/reference/features/transaction_reporting.html
The Merchant Web Services API (GetReturns) will be removed on July 20th, 2016. From that date forward all requests to https://account.authorize.net/api/merchantapi.asmx will return a response with status code 410 Gone. On August 20th the endpoint will be removed completely. Our standard Reporting API methods of GetTransactionList and GetTransactionDetails can be used to return the same returns data as returned in the GetReturns API.