All Legacy API credential questions here please.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To request API Signature or Certificate credentials for your PayPal account:
3. Click My selling tools
4. In the API access section, click Update.
5. Under NVP/SOAP API integration, click Manage API credentials.
- If you have already generated an API Signature, then View API Signature appears. Click that option to view or remove your existing API Signature.
- If you have already generated an API Certificate, then View API Certificate appears. Click that option to view or remove your existing API Certificate.
- Select one of the following options, then click Agree and Submit.
- Request API Signature – Select for API Signature authentication.
- Request API Certificate – Select for API Certificate authentication.
- PayPal generates your API credentials as follows:
- API Signature credentials include an API Username, API Password, and Signature, which does not expire. These values are hidden by default for added security. Click Show/Hide to toggle them on and off. When finished, click Done.
- API Certificate credentials include an API Username, API Password, and Certificate, which expires automatically after three years. Click Download Certificate to save the API Certificate to your desktop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_profile-api-access
this one is not working anymore?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, that link will bring you to the main page where you have few option to choose from for the APIs, you can login into your Sandbox account and then click that link you posted, you will see the page I mean.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These instructions appear to be a little out of date... I'm looking to update my old Classic API credentials. When I click on this:
I get to this screen:
and as you can see, the only option is to "Remove". I am worried that since this is a legacy API, removing them might be permanent with no option to refresh or create new ones. As this is mission critical and in production, I don't want to risk that. Does anyone know if this is the case?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @BrianDunning,
I'd suggest you reach out to Merchant Technical Support who can assist you with the steps to update your integration.
Christina
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The Merchant Technical Support is no longer exist, but I hope I can get some help/clue here.
I have access to the sandbox API, but when I wanted to request API Credentials for Live Account, after "Manage API credentials", it says "Sorry, we couldn’t confirm it’s you.".
I never get the SMS Verification codes also.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Christina is right, open a ticket with us and we can discuss, removing your API credentials on a live integration will likely break the integration and require you to replace the API credentials in your software, it's quick enough to do this, but you want to make sure you know where you need to update before you remove any existing credentials.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i cant find this option " In the API access section, click Update. " in my business account settings option. am from Nigeria.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I am having trouble getting legacy API NVP/SOAP credentials. Why am I trying to use the legacy API? Well, I am using an old WordPress plugin that has built-in PayPal payment functionality, and it is designed to use the NVP/SOAP api. Why am I using this old plugin? Well, there unfortunately isn't an alternative plugin that offers the same functionality. So I'm basically stuck - I need the legacy API.
When I try to generate NVP/SOAP credentials, it doesn't generate an API Password and an API Signature. Instead, it appears to generate REST api credentials, a "Client ID" and "Secret".
I attempted to use these values anyway with the assumption that "Client ID" corresponds to "Password" and "Secret" corresponds to "Signature", but it does not appear to work. I am not 100% positive that the plugin itself is not the problem, but I do fear that it is just not possible to generate NVP/SOAP credentials anymore.
Is the NVP/SOAP api still supported? Please advise.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @RockStump,
NVP/SOAP integrations are definitely still supported. Where are you when you're generating those credentials? I just went to reproduce what you're experiencing and I cannot. For reference:
Log in to paypal.com
Hover on your name to display the drop down menu.
Click Account Settings and then on API access select Update.
Scroll until you see "Custom checkout experience" and you're going to select the Classic integration [click Manage API Credentials]
You should see the below view where you can generate your NVP/SOAP API Username, Password, and Signature.
Hope this helps!
Christina
- « Previous page
-
- 1
- 2
- Next page »
Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
- Saved paypal payment integration in REST APIs
- Need advice on Account / Donations / Payouts / technical issues in Sandbox Environment
- Subscription Status Immediately Updates to New Plan Despite Payment Scheduled for Next Billing Cycle in NVP/SOAP APIs
- Subscription API doesn't support updates? in REST APIs
- Assistance Needed with Handling Future Subscription Payments Without User Interaction in REST APIs