I created an app in my PayPal developers account by going to My Apps & Credential > Rest API. I gave the app the Transaction Search app feature option but I am getting permission issues.
Is there something that I might be missing?
Related
We are using SignIn with Google on our Flutter App that uses AWS cognito. Recently it started giving error:
"Error 403: access_denied The developer hasn’t given you access to this app. It’s currently being tested and it hasn’t been verified by Google. If you think you should have access, contact the developer"
The app was in "Testing" and seems to have reached the limit of 100 users. In order to have more than 100 users use the SignIn with Google option, we need to put the Google Authentication App to "Production". In order to do that Google is asking for domain verification of the amazoncognito.com used in "Authorized redirect URIs". Since we don't own this domain we can't verify it.
Can someone please help with how can we get the verification of the GCP "oauth consent screen" done with other domains like amazoncognito.com?
Thanks in advance.
I don't think this is currently possible.
Your best bet would be to file a feature request with Google for a supported verification progress for third-party user identity services.
I would suggest using the Google Workspace add-ons component for this type of request.
I have a web app and I use Facebook's Account Kit for authentication. If I delete my personal Facebook account, what happens to my Facebook developer account? Will Account Kit's API still work?
Your AccountKit setup is tied to one app that you have already set up and should be able to see in your Developer Dashboard.
It is a requirement for each app to have at least one valid Administrator. You should be able to delete your account, as long as you made sure to add someone else as an Administrator (and confirm that they accepted the request).
after a lot of back and forth with the Twitter documentation I am now able to authenticate with OAuth 1.0 and make request behalf on the user who sign-ined and accepted my app to preform changes / retrieve data.
Now, I'm trying to make requests to the Twitter Ads API.
This is the error I get:
{"errors":[{"code":"UNAUTHORIZED_CLIENT_APPLICATION","message":"The client application making this request does not have access to this API"}],"request":{"params":{}}}
As it seems, there is a need of another app registration. I registered it with my app id, assuming the 'developer' stage is the fit for me. I'm trying to retrieve analytics, e.g., retrieve campaigns for the user who accepted it.
After registration the Ads App Form, the error stays the same. The docs don't specify if there is a need for a special implementation for the ads-api. Also, the Ads App I opened isn't mentioned anywhere, nor in my twitter apps.
Am I missing something?
Thanks before.
Looking at Twitter ads API documentation, getting access is a pretty involved process. From their site, you'll need:
One positive referral from a client, advertiser or Twitter team
(outside of Ads API)
Clear value proposition on how how your solution
will supplement the Twitter ads offering and improve advertiser
performance
History of compliance with Twitter developer policies
Experience running Twitter Ads
Twitter App ID associated with a corporate #username, with no more than 5 active tokens
It seems a little overkill, but I haven't seen any other way around it. If you find a better way to get ads API access, please post another answer here because I have a potential project that would use these APIs, but the application process has been too daunting to really justify starting the effort.
As of Sept 2016, the application process appears to be much easier.
It appears you no longer need positive referrals, value props, history, or experience running Twitter ads.
Currently I have used the sandbox App Id and test credentials successfully to make API calls, however now I would like to switch to the live version. I looked at the check list and believe I switched out all the sandbox information to live credentials. However the last thing I need to switch out is the APP - ID. I created an App which has the status of "approved" in paypal developer however I'm not sure where to get the App - ID for it. In addition, should I be seeing the app in the Manage Classic Apps? I see it in My Apps on the developer page, but not in that section. Thank you very much for the help.
Select My Account > Profile > My Selling Tools, then click the Update (API Access) link
Click Request API Credentials on the API Access page
Select Request API signature and click Agree and Submit to generate a set of Signature credentials
More information can be found at: https://developer.paypal.com/webapps/developer/docs/classic/api/apiCredentials/
EDIT:
You will need to use the classic api to obtain an APP-ID. The new API does not use APP-ID's, but instead client ID's which are extremely different.
For testing my adaptive api payments with new sandbox (Developer.Paypal.com) i have imported my sandbox accounts into the live paypal account. But on testing the payment i am not getting redirect to the PayPal Store page. Instead it asks me to login into http://developer.paypal.com on which i am already login. Even when i does login it do not show me the store page for the payment but instead just show me the homepage for the developer site.
https://www.sandbox.paypal.com/webscr?cmd=_ap-preapproval&preapprovalkey=PA-30G61643G7253031W
Above is the URL which i got as result of testing for payment from my site along with the approval key. But i am just moving in the circles of this new paypal transition. As i have also tried deleting my cookies on the Mozila. I am using iMac.
Same happens when i try to go to sandbox site from inside the live account, it sends me to the sandbox site where i get message to login into the developer.paypal site
Please advise how to get rid of these PayPal bugs for testing the Workflow which earlier was working smoothly untill PayPal decided to roll out new changes (Required Live account for testing).
Looking for guidance on this issue.