@sean I see where the documentation might be failing you. "choices" isn't a path parameter, it's a "form data parameter", which means it needs to be encoded in the request like form-data https://davidwalsh.name/curl-post-file
Top-level
@sean I see where the documentation might be failing you. "choices" isn't a path parameter, it's a "form data parameter", which means it needs to be encoded in the request like form-data https://davidwalsh.name/curl-post-file 6 comments
@sean they do label them separately -- this is partly just a problem with form-data in REST APIs. It's confusing. @darius ah, you’re right. I’m still pretty new to this - it can be confusing as to which is which. Most of the documentation is stellar, and has been really helpful in building my understanding further. @sean one thing that I wish all REST API endpoint documentation had was a valid example curl request that you can test against. @darius gosh, I feel so silly now. Simply updating my request to “data” instead of “params” 100% fixed it. 😅 Oh god, is this what being a developer is like? 😭 |
@darius oh, that’s kind of confusing.
Usually, when I see “Params”, I kind of assume it means “request params”.