- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're currently experiencing a complete failure of the SOAP API, which we use to create CIM profiles using the authorizesauce Python library.
It was working as of 10:45 a.m. central time this morning (April 18th.) It suddenly started failing at some point afterwards. Both our production and sandbox accounts simply return a 550 error with no other information when we attempt to create a CIM profile. We are able to, e.g., charge existing profiles, however.
Is there an issue with the SOAP API currently?
Solved! Go to Solution.
04-18-2018 04:15 PM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All ,
We have fixed the issue with the SOAP APIs . Let us know if still any issues .
Going forward I will strongly recommended to look at integrating using our official Authorize.Net SDKs at https://github.com/AuthorizeNet
Also we are planning of doing end of life for the deprecated SOAP APIs in future so if there is direct integrations with SOAP APIs please look to move to use our SDKs or XML APIs at https://developer.authorize.net/api/reference/index.html
More details will be communicated on it soon .
Thanks
Anurag
Send feedback at developer_feedback@authorize.net
04-20-2018 08:07 PM - edited 04-20-2018 09:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @jaearess
I've escalated your report. You should also contact customer support and open a case with them as well.
Richard
04-18-2018 06:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. We have contacted support already.
04-18-2018 06:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're experiencing the same with both AuthorizeSauce and our ERP system which also uses the SOAP API.
04-18-2018 07:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same for us using soap!
Thanks for this post, been chasing this down all day!
04-18-2018 10:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Can you provide more details on the errors being receieved ?
If you have any error logs or error messages please provide in the post along with if you are using any SDKs or direct integration with SOAP .
Thanks
Send feedback at developer_feedback@authorize.net
04-18-2018 10:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only error message we receive is "Unknown" when using the sandbox. In production, there's no error message at all. In both cases, the error code is 550.
We're using the authorizesauce Python library, which uses the Suds SOAP client Python library internally.
04-18-2018 10:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As additional information, there's been an issue opened on the authorizesauce Github: https://github.com/drewisme/authorizesauce/issues/48
That includes code that reproduces the error.
04-18-2018 10:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this issue only reported via the authorizesauce integration ? or have we seen this through other integrations also ?
Also I am seeing this repo hasnt been updated from May , 2016 .
Our internal tests with SOAP dont seem to be showing any issues .
I will suggest to use our Authorize.Net SDKs if possible going forward .
https://github.com/AuthorizeNet/sdk-python
https://github.com/AuthorizeNet/sample-code-python
Send feedback at developer_feedback@authorize.net
04-18-2018 11:02 PM - edited 04-18-2018 11:04 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Only using in production.
Can see 2 payments went through this morning around 6am pst and nothing since, all are failing as soon as it tries to manage profile.
PaymentProcessingProfileMaintenence Failed [Exception Occured, The request failed with HTTP status 550; .]
Talked to support twice today and said no issues reported...just submitted case and referenced this thread.
Case Number: 05001634
Thanks!
-R
04-18-2018 11:06 PM

