I got the following error:
{ "status": "error", "message": "Invalid botname"}
When I am using the Pandorabot CLI. My bot name and my setting name are the same, so do you have any idea on where the problem is?
I got the same error today, when I used upper case in the name. Try use only lower case.
Related
I was trying google APIs to create a new sheet but I am unable to achieve the goal
the error I am getting is
Invalid spreadsheet. spreadsheet: This user did not create this id.
so I thought I am doing something wrong did some research I got this link (https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets/create) and tried it here (Try it! button) it gives the same error
{
"error": {
"code": 400,
"message": "Invalid spreadsheet.spreadsheetId: This user did not create this id.",
"status": "INVALID_ARGUMENT"
}
}
What am I doing wrong?
Just performing the following request will create a spreadsheet:
POST https://sheets.googleapis.com/v4/spreadsheets
No need to pass something in the body. The documentation is a bit confusing on that point as it says you should send an instance of Spreadsheet in the request body. But you don't have to.
I tried to follow the online guideline to do the hosted session integration.
When testing Retrieve session api using postman, the error occurred.
{
"error": {
"cause": "INVALID_REQUEST",
"explanation": "Unexpected parameter 'merchantId'"
},
"result": "ERROR"
}
I did settle the correct parameter, merchantId and sessionId.
https://ap-gateway.mastercard.com/api/documentation/apiDocumentation/rest-json/version/latest/operation/Session%3a%20Retrieve%20Session.html?locale=en_US
You don't actually include the text "merchantId". You have to provide a valid merchant ID. Click on the "URL Parameters" tab on the link you posted.
{merchantId} Alphanumeric + additional characters COMPULSORY
The unique identifier issued to you by your payment provider."
The same goes for "sessionId".
I'm trying to use cloudbilling.billingAccounts.testIamPermissions in the APIs Explorer, but I get an error.
API URL
https://developers.google.com/apis-explorer/?hl=ko#p/cloudbilling/v1/cloudbilling.billingAccounts.testIamPermissions?resource=billingAccounts%252F01183E-6A3E97-BE2C7A&resource=%257B%250A%257D&_h=1&
Error Result
{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT"
}
}
The error message appears as 'Request contains an invalid argument', so the value entered in resource seems to be incorrect.
I entered billingAccounts / {billingAccountID} for resource, but I do not know why I get an error.
{billingAccountID} has entered the billing account ID you are using.
What value should be put in the resource?
You need to use your full ID "billingAccounts/012345-567890-ABCDEF`" as an string. Also avoid to share your private information for security reasons use examples instead.
Confirm that the other options of the API works for you.
I have a raml doc the specifies my request data structure with a field like the following:
"EstInstallDate": {
"description": "the estimated date that the installation will be completed",
"type": "string",
"format": "date"
}
this is great, because when the APIkit is hit, a MessageException is raise with the following text:
string "2016-32-32" is invalid against requested date format(s)
yyyy-MM-dd
but the generic 400 error payload is jsut "bad request" I would like to include this error message in the response payload.
how do i do this?
I found that in my exception block i can access
exception.message
to get the full string of the error. however, it would be great to include which field failed the validation
I updated our BigQuery client to new client Google API and suddenly I started seeing this error when uploading via JSON:
"errors": [
{
"reason": "invalid",
"location": "Offset:0 / Line:1 / Column:159 / Field:q1",
"message": "Could not convert value to string"
},
Job reference:
"jobReference": {
"projectId": "dot-metrics",
"jobId": "job_8e0511a40c1845cca5717daf78b605f7"
},
This worked before we updated our client, afterwards it just stopped working so it must be some change inside BigQuery. Any help is appreciated!
This looks like a regression in a recent release that broke importing null values in json. A fix should be forthcoming.
Note if you drop the null fields (i.e. instead of "field: null" you just don't include "field" at all) it should continue to work.