/soap/v1/* → endpoint removal
Authorize.net API
Deprecated, no date
Authorize.net has deprecated the SOAP API without a shutdown date. This deprecation affects all requests to the /soap/v1/* endpoint. Once shut down, calls made to these endpoints fail.
Calls it hits
/soap/v1/*
What to use instead of these calls
Send the same operations to the Authorize.net API (XML or JSON) at POST /xml/v1/request.api.
In Authorize.net API's words
AIM | Deprecated | Authorize.net API | SOAP API | Deprecated | Authorize.net API | SIM | Deprecated | Accept Host |
Facts
- API
- Authorize.net API
api.authorize.net - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Authorize.net API's own pages
Questions
When does this change take effect?
Authorize.net API deprecated /soap/v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Authorize.net API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Authorize.net API 1
-
No date
POST /xml/v1/request.apiEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.