JSON/REST, POST organizations.json 406 not acceptable

Answered

Comments

5 comments

  • Avatar
    aderyabin

    Anyone have decision for this mistake. I tried to use various content-types, but I have the same problem.

     

  • Avatar
    Steven Yan

    Our organizations API is not responding to JSON POST requests properly.  A workaround for now is to actually pass .xml on the end of the API request like below.  Note the .xml passed on the end of the controller, but with JSON header and body:

    curl -u username@domain.com:password http://steven.zendesk.com/organizations.xml -X POST -H "Content-Type:application/json" -d "{\"organization\":{\"name\":\"Test2\", \"is_shared\":false}}" -v

    We'll make sure we fix the creation via JSON to behave as expected.

  • Avatar
    NambiBalasubramaniyam

    @Steven -  Is there any update on this issue?  Is this still on a workaround or a fix is already available?

     

    Thanks.

    Nambi

  • Avatar
    Steven Yan

    Nambi, this has yet to be worked on, sorry for the delay.

  • Avatar
    Steven Yan

    Nambi, it looks like I spoke too soon. We have been doing some versioning and refactoring work on our API and it looks like this is now fixed.

Please sign in to leave a comment.

Powered by Zendesk