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)
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.
Greetings and thank you for tending to this question!
I am trying to have my Discord bot create a Scheduled Guild Event.
A Calendar event for players and attendees to join a voice channel.
I am trying to achieve that by doing a POST call to Discord's API, and I am failing with the following error.
The following message was produced from a Postman test.
{
"code": 50109,
"message": "The request body contains invalid JSON."
}
As the message implies something is off with my JSON body.
Below follows a version of the JSON body I am trying to send!
{
"name": "The Bot created this!!!",
"privacy_level": 2,
"scheduled_start_time": "2022-06-15T15:00:00+00:00",
"description": "The Bot also described this!!",
"channel_id": 980830611458426901,
"entity_type": 2
}
I tried to follow the API's documentation as perfect as I could with no positive results!!
If you wish to follow the documentation yourselves here's the link:
Create Guild Scheduled Event
I am definitely missing something or adding something that should be added to the JSON body
of a different type!!! Any insights welcome!
What I know and tried
My authentication is solid because I am able to GET all events present.
Many variations of single quotes '' and type declarations for the data in the JSON body.
Regardless of insights, Thank you for your time!!
I am trying to retrieve the results of a completed Google survey. Using this url/resource per the google docs: I get the same error when attempting through the Google playground.
Get: https://www.googleapis.com/consumersurveys/v2/surveys/{my surveyurlID}/results.
I get the following error:
"domain": "global",
"reason": "INVALID_VALUE",
"message": "Invalid Value supplied to API:
Authentication token is same as used to get the survey meta data ( which works).
Not sure what value is invalid. Any help appreciated.
Unfortunately, the "try it now" widget doesn't support media downloads and we currently only provide the results as an excel file.
In order to get the results you'll need to specify a media type in your request. You can do so with the following endpoint:
GET https://www.googleapis.com/consumersurveys/v2/surveys/survey_id/results?alt=media
I would recommend using an OAuth 2 library to authenticate and then accessing the above endpoint.
We'll work on improving the documentation and clarifying this.
Thanks for bringing this to our attention.
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 experimenting with Paypal REST API and I was stunned into a problem with webhooks.
I trying use the following tactic to verify event data - ensure that HATEOAS link with rel == "self" like https://api.sandbox.paypal.com/v1/notifications/webhooks-events/WH-6L177801XL962315K-5B870910V53268712 is present, and ensure that this link starts with expected API endpoint (set in web.config) and reloads event data with it, and use it as trusted event data.
But this tactic fails, it results to 404 instead of getting webhook data.
Who else used Paypal REST API webhooks? How you are verify that the event come from trusted event source?
Update
Was able to get more details on messages received. Response body:
Data [{\r\n \"name\": \"INVALID_RESOURCE_ID\",\r\n \"details\": [],\r\n \"message\": \"Resource id is invalid\"\r\n}]
Headers as JSON object: [{\r\n \"PROXY_SERVER_INFO\": [\r\n \"host=slcsbplatformapiserv3002.slc.paypal.com;threadId=370534\"\r\n ],\r\n \"Paypal-Debug-Id\": [\r\n \"e33a2f285d46f\"\r\n ],\r\n \"SERVER_INFO\": [\r\n \"webhooksplatformserv:ppaas_1_2.v1.notifications.webhooks-events.id.GET&CalThreadId=184&TopLevelTxnStartTime=14b4099eb05&Host=slcsbwebhooksplatformserv3002.slc.paypal.com&pid=29135\"\r\n ],\r\n \"Date\": [\r\n \"Sat, 31 Jan 2015 15:26:44 GMT\"\r\n ],\r\n \"Server\": [\r\n \"Apache-Coyote/1.1\"\r\n ]\r\n}]
The hateoas link should return the same payload as the original webhook event. So there seems to be some issue there.
However, if your intention is to validate if the event came from PayPal then the correct way is to validate the signature included in the webhooks header. This link has more details around the security aspects in webhooks.
https://developer.paypal.com/webapps/developer/docs/integration/direct/rest-webhooks-overview/#event-security