Bad Request response for api/cla/getAll
See original GitHub issueBased on #166, I created a request to https://cla-assistant.io/api/cla/getAll
and set the x-token
header to be an access token that has access to my org. I’ve confirmed that the CLA Assistant app has proper permissions, as well as organization access. When I pass the following as the request body:
{
"orgId":"682240",
"gist":{
"gist_url":"https://gist.github.com/a072029a2c59d6d25e774921fa1d88d1"
}
}
I receive the following response:
{
"message": {
"code": "400",
"status": "Bad Request",
"message": "Empty value for parameter 'id': undefined"
}
}
Can someone help me understand why the request is bad and how to fix it?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Bad Request 400 when trying to get all users. Dto and form
My userService checks if user is administrator, then allow to getAllUsers in List. When I want to get all users, I get Bad...
Read more >REST API for JD Edwards EnterpriseOne AIS Server
REST API for JD Edwards EnterpriseOne AIS Server. ... Get All Orchestrations v3. get. /jderest/v3/open-api- ... Response. Bad Request - Invalid JSON Input...
Read more >How to Fix a 400 Bad Request Error (Causes and Fixes) - Kinsta
The 400 Bad Request error indicates that the server cannot or process the request due to a client error. Read about the common...
Read more >Response status code does not indicate success: 400 (Bad ...
The remote server returned an error: (400) Bad Request. Description: An unhandled exception occurred during the execution of the current web ...
Read more >Contact Search API 400 Bad Request when fetching records ...
The answer is in the documentation: "The search endpoints are limited to 10,000 total results for any given query. Attempting to page beyond...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
indeed, it doesn’t work currently. This API should still work for repos but it’s broken for orgs. Sorry for that. I’ll fix it in the next release. It could take a one or two weeks, though. I hope you don’t depend on it.
In the changelog for 1.7.0 I see this issue reference. I tried my call again, but now I get the following response:
Which org or repo is this message referring to? For the org in question, I’m an owner and have admin access to all repos.