PayPal REST API (api.paypal.com)
NVP/SOAP API removal
Deprecated, no dateSubscribe to PayPal REST API (api.paypal.com)Share
PayPal has deprecated the legacy NVP/SOAP APIs, including the /nvp endpoint, without a shutdown date. Although PayPal continues to support them for now, the interface is slated for removal and affected calls will eventually fail.
Calls it hits
/nvp
What to use instead of these calls
Move to the REST APIs: Orders v2 (/v2/checkout/orders) and Payments v2 through PayPal's upgrade hub. The move requires more than changing an identifier, as the REST APIs require a REST app client ID and secret instead of 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 REST API (api.paypal.com)'s words
Deprecation notice: PayPal's NVP/SOAP APIs are legacy APIs, but PayPal continues to support them.
Facts
- API
- PayPal REST API (api.paypal.com)
api.paypal.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PayPal REST API (api.paypal.com)'s own pages
Questions
When does this change take effect?
PayPal REST API (api.paypal.com) deprecated /nvp without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PayPal REST API (api.paypal.com) 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.