topic Re: XML Support in AIM API at new URL in Integration and Testing

XML Support in AIM API at new URL

RyanNovak — Wed, 17 Sep 2014 15:49:43 GMT

So many initialisms. :)

Anyway, I received an email from Authorize.net saying that the old XML API server's IP address was being retired, and that I should switch over to the new URL (secure.authorize.net/gateway/transact.dll). However, when I did so, I found that the server returns a blank response when I submit transaction info via XML. Should I take this to mean that the old XML API is being retired as well, or is there some other change that is preventing my old code from working?

Further info: The code in use is based on the Authorize.net sample XML PHP code, which would have been current as of December 2011. It's been running problem-free since then using the old URL (api.authorize.net/xml/v1/request.api).

Re: XML Support in AIM API at new URL

Joy — Wed, 17 Sep 2014 21:36:54 GMT

Hi RyanNovak,

The XML interface is not changing, only the location. We always recommend connecting by URL, as the IP address can potentially change without warning.

Thanks,

Joy

Re: XML Support in AIM API at new URL

RyanNovak — Thu, 18 Sep 2014 00:17:19 GMT

I do connect via the URL (api.authorize.net/xml/v1/request.api). Is the URL itself being phased out, or just the IP address it's currently using? I guess the appropriate question is: do I actually have to do anything?

Re: XML Support in AIM API at new URL

RichardH — Thu, 18 Sep 2014 01:38:19 GMT

If you are using a URL as opposed to a specific IP address, you don't need to do anything.

Richard

Re: XML Support in AIM API at new URL

RyanNovak — Thu, 18 Sep 2014 19:51:03 GMT

Excellent, thanks for the info!