The NVP/SOAP API is deprecated
PayPal
Deprecated, no date
PayPal has deprecated the NVP/SOAP APIs without a shutdown date, noting that it continues to support them as legacy APIs. When support eventually ends, affected calls to the interface will fail.
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 identifier, as the REST APIs require a REST app's client ID and secret instead of the NVP/SOAP API credentials.
The REST APIs need a REST app's client ID and secret in place of the NVP/SOAP API credentials.
In PayPal's words
Deprecation notice: PayPal's NVP/SOAP APIs are legacy APIs, but PayPal continues to support them.
Facts
- API
- PayPal
api-3t.sandbox.paypal.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PayPal's own pages
Questions
When does this change take effect?
PayPal deprecated these calls without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PayPal 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.