I'm trying to use the GoDaddy Purchase Domain API on their OTE environment, but I keep getting the error below, which suggests that some payment is required:
{
"code": "INVALID_PAYMENT_INFO",
"message": "Unable to authorize credit based on specified payment information"
}
How can I go around this problem?
I ended up reaching out to their customer support, and they made some changes on their end that allowed me to proceed.
Related
I'm going through a weird error when making a simple GET request using the Shopify REST Admin API. When I query with a GET request {store_url}/admin/checkouts.json I can get all the checkouts. Now, when I query admin/api/2023-01/checkouts/<checkout_token>.json I get this error { "errors": "[API] This action requires merchant approval for read_checkouts scope." }
I'm using the same store, same key. Its access scope is read_orders, a custom/private app.
Any clue?
I tried swapping using the checkout id, checkout token, checkout key. I also tried calling the orders endpoint using the checkout token and id. No luck so far.
Your App does not have the needed scope read_checkouts
If you add that scope to the App your call to the checkout endpoint will work.
I have a subaccount that has a domain in the "redemption" state after it expired, and I would like to "redeem" it so I can renew it. From looking in the API docs, it is only available in the v2 API, and I was able to get started in the v2 API with some help. However, even with the correct UUIDv4 customer ID for the domain, I get the error: { "code": "ERROR_INTERNAL", "message": "Internal Server Error"}
The POST body is not labelled as required in the docs, but it is required. To get details on each of the fields, you need to click on the button (which is easy to miss) that switches between "Example Value" and "Model" (screenshot)
I have just login to Yodlee platform and exploring the API, I have gone through the quick start and test drive, now I'm getting the InvalidSearchIdentifierException when I'm just using default values provided by test drive sample app. The error shown is
{
"errorOccurred": "true",
"exceptionType": "com.yodlee.core.transactionsearch.exceptions.InvalidSearchIdentifierException",
"referenceCode": "_47ee0b3c-ea92-4a7a-9ba7-0a02bad49d47",
"message": "Invalid argument value: com.yodlee.core.transactionsearch.TransactionSearchIdentifier#21d77397"
}
but according to the documentaion the search identifier is 192168210225-1377612242609--1002083317-TX_SEARCH mentioned in link
please anybody tell me why I'm getting this error
anyway testdrive app is here
You are using getUserTransactions API, so I assume you want to get user's transactions. You should be using excuteUserSearchRequest API to get the user's transactions, getUserTransactions API should be used when you user has more than 500 transactions as excuteUserSearchRequest API returns transactions in batches of 500. For more details refer this.
I'm using the http://developer.yodlee.com/TestDrive developer Test API module and using one of the 5 dummy accounts provided by Yodlee, For a particular user I have managed to add a dummy DAG bank account and one real bank account which is visible in getAllSiteAccounts details Api so its obvious that site have been added.
But while using the getUserTransactions API I'm getting error
{
"errorOccurred": "true",
"exceptionType": "com.yodlee.core.transactionsearch.exceptions.InvalidSearchIdentifierException",
"referenceCode": "_567afa0b-9d5a-4fb4-9db1-afd4f43c39c2",
"message": "Invalid argument value: com.yodlee.core.transactionsearch.TransactionSearchIdentifier#2ad082d0"
}
I also tried using the executeUserSearchRequest still didn't get any transaction details
{
"searchIdentifier": {},
"numberOfHits": 0
}
Can you please guide me If I'm using the API's correctly ?
You should use executeUserSearchRequest API to get the transactions. You should check the date range you have provided while searching for transactions and also try to remove itemAccountId.identifier and then search, you should get the transactions.
I'm having the same issue the only difference though is that I don't have any issues on DAG accounts, but when I used our production account I can't get the user transactions. I was reading this post Get all user transactions with executeUserSearchRequest and I guess the solution is to make sure that your server/code have the same timezone configuration.
On the page in which the selection for payment method is made, paypal is not working. It used to work and i actually received a payment last monday, the 18th of March.
But now when i click on "pay with paypal", the page keeps loading and eventually sends this message to clients ;
Please try to contact the merchant:
PayPal response:
->
So the module has actually worked before but seized to work all of a sudden. Prestashop 1.4.7.3, PayPal 3.4.6
Try this: in modules/paypal/api/paypal_connect.php, look for "verbose", and set it to "false" instead of "true".
It should work.
Let's read this about the same problem:
"When you don't have any error messages it is because PayPal did not send any response. This error appends when your server IP has been banned from PayPal. This error often occurs when you are on a shared hosting platform because of hacks attempts but it could also occurs on dedicated hosting for the same reason" (http://forge.prestashop.com/browse/PNM-1199?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#issue-tabs)
Try to use another server with another IP. There is a man that said that it works (http://forge.prestashop.com/browse/PSCFV-8608?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#issue-tabs)
This error because of no return in both functions inside
paypal/api/paypal_connect.php
_connectByFSOCK
_connectByCURL
Both these functions are return false may be differences are between Certificate and Signature but remember Signature is the preferred way of accessing PayPal API.
you should check $url and #host in the above image may be not available any more.. in my case I changed mode to live and working fine but still in testing mode not working ... I think because of PayPal API not wor