Closed danieledler closed 8 years ago
Hello,
well, these routes are weird a little bit. If you use JSONP, you should use /jsonp/project/updateInfo/:id but if you use the JSON, then you have to use /json/project/updateInfo and put a "projectId" field to the request. I know it's very ugly... It has historical reasons... :/
Hi! Thanks, that works! (I tried combinations with projectId too, at least adding it in the url, but I must have missed setting it in the body.)
I'm trying to update the title for a project but I get the response
In the docs, you have required parameter field
data
of typeProject
, where theProject
model has an_id
field. So I tried sending the data asFor the
/json/project/createFromDefaults
route, this works, but that route also has_id
next todata
as required parameters in the docs.Looking at the JS API, the jsonp request doesn't call
/jsonp/project/updateInfo
as in the docs, but/jsonp/project/updateInfo/:projectId
, so I also triedjson/project/updateInfo/5729c3528a95db2a23f9fc16
but that resulted in a404
response.