PayPal NVP/SOAP API removal
Deprecated, no dateSubscribe to PayPal NVP/SOAP APIShare
PayPal deprecated the NVP/SOAP APIs without a shutdown date. While described as legacy APIs that PayPal continues to support, affected calls to api-3t.paypal.com will eventually fail under this removal. No effective cutoff date has been announced.
What to use instead of these calls
Move to the REST APIs, specifically Orders v2 (/v2/checkout/orders) and Payments v2, using PayPal's upgrade hub. The migration requires more than changing an endpoint, as the REST APIs require a REST app's client ID and secret instead of your existing NVP/SOAP credentials.
The REST APIs need a REST app's client ID and secret in place of the NVP/SOAP API credentials.
In PayPal NVP/SOAP API's words
Deprecation notice: PayPal's NVP/SOAP APIs are legacy APIs, but PayPal continues to support them.
Facts
- API
- PayPal NVP/SOAP API
api-3t.paypal.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PayPal NVP/SOAP API's own pages
Questions
When does this change take effect?
PayPal NVP/SOAP API deprecated the NVP/SOAP API without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PayPal NVP/SOAP 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.