We are integrating with eCheck and the Reporting services using C# .NET AuthorizeNet NuGet package.
ECheck is authenticating fine, calls to the Reporting service are failing with the E00007 error.
I am using the ApiKey and TransactionKey specified in a constant for both calls, so I know the same values are being used in both.
Examining both calls using Fiddler2 I have confirmed the following:
The eCheck call is being sent to https://secure.authorize.net/gateway/transact.dll.
The Reporting call is being sent to https://api.authorize.net/xml/v1/request.api
I have confirmed that the ApiKey/TransactionKey values are passed correctly into the <merchantAuthentication><name>]</name><transactionKey></transactionKey></merchantAuthentication> elements.
This is a production account.
Any ideas on where I can look next to resolve this?
05-31-2013 03:27 PM
Can you see the request param in Fiddler2?
05-31-2013 03:55 PM
Here is the raw request, with the actual keys redacted:
POST https://api.authorize.net/xml/v1/request.api HTTP/1.1
Content-Type: text/xml
Host: api.authorize.net
Content-Length: 489
Expect: 100-continue
<?xml version="1.0" encoding="utf-8"?><getSettledBatchListRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"><merchantAuthentication><name>redacted</name><transactionKey>redacted</transactionKey></merchantAuthentication><firstSettlementDate>2013-05-01T07:00:00Z</firstSettlementDate><lastSettlementDate>2013-05-31T07:00:00Z</lastSettlementDate></getSettledBatchListRequest>
05-31-2013 04:42 PM
The only thing I see is the Expect: 100-continue
05-31-2013 05:19 PM