As the TLS 1.2 update looms, I was frustrated to find I couldn't easily determine if we were on the Janary 30 or Feb 8 test group for TLS 1.2.
Where can you determine the endpoint that our servers are passing API calls for AIM and CIM transactions? I assume this is listed somewhere – either in the API code or in documentation somewhere.
I have a folder called /sdk-php-master that is where the code lives, but how can I determine my endpoint from these lists?
Thanks!
Jan 30, 2018 – Readiness Window – Akamai Hosted (9am - 1pm PT)
February 8, 2018 – Readiness Window – Non-Akamai Hosted (11am - 1pm PT)
01-29-2018 01:46 PM
Normally, the endpoint for AIM/CIM/ARB XMLor JSON requests would be -
https://api.authorize.net/xml/v1/request.api - For Non-Akamai
OR
https://api2.authorize.net/xml/v1/request.api - for Akamai
Check out more details about here- Akamai
I just looked at the SDK for php, endpoint host is defined in the following file.
is this what you are looking for?
-Bhavana
01-30-2018 03:16 PM
Bhavana,
Thanks for the response. I found the file you pointed out which makes sense, but I also see the following in the AuthorizeNetCIM.php. Which seems to say that there may be more than one ultimate endpoint if you use both AIM and CIM calls. The CIM one matches the endpoint in the /constants/ file, but the AIM one points to a different endpoint.
/** * A class to send a request to the CIM XML API. * * @package AuthorizeNet * @subpackage AuthorizeNetCIM */ class AuthorizeNetCIM extends AuthorizeNetRequest { const LIVE_URL = "https://api.authorize.net/xml/v1/request.api"; const SANDBOX_URL = "https://apitest.authorize.net/xml/v1/request.api";
and also in the AuthorizeNetAIM.php file:
/** * Builds and sends an AuthorizeNet AIM Request. * * @package AuthorizeNet * @subpackage AuthorizeNetAIM */ class AuthorizeNetAIM extends AuthorizeNetRequest { const LIVE_URL = 'https://secure.authorize.net/gateway/transact.dll'; const SANDBOX_URL = 'https://test.authorize.net/gateway/transact.dll';
So if these are my two endpoints, I fall on the Feb 8 testing date for TLS disable.
01-30-2018 03:28 PM - edited 01-30-2018 03:30 PM
I have missed pasting the endpoints for the AIM. But, thanks for finding them though.
Normally all the anet api requests (Payments, Subscriptions,CustomerProfile) goes to https://api.authorize.net/xml/v1/request.api.
AIM, SIM method requests goes to endpoint - https://secure.authorize.net/gateway/transact.dll. But, we recommend you moving away from AIM.
Check out - https://developer.authorize.net/api/upgrade_guide/
-Bhavana
01-30-2018 04:46 PM
@bhav wrote:I have missed pasting the endpoints for the AIM. But, thanks for finding them though.
Normally all the anet api requests (Payments, Subscriptions,CustomerProfile) goes to https://api.authorize.net/xml/v1/request.api.
AIM, SIM method requests goes to endpoint - https://secure.authorize.net/gateway/essays.agency.dll. But, we recommend you moving away from AIM.
Check out - https://developer.authorize.net/api/upgrade_guide/
-Bhavana
Hello Bhavana,
Does the Authorize.Net API support JSON? How does it work then? I've been looking for the variants here, but there're so many details to consider that I'm at a loss.
Adrian
08-22-2019 09:48 PM - edited 08-22-2019 09:50 PM