400 Bad Request when adding collaborations via Box CLI

Answered
New post

Comments

2 comments

  • michellarcari

    I think I found the problem: the role is not mandatory when using the CLI but if you don't pass that argument it will fail. I was able to successfully add the collaboration by informing the role

    0
    Comment actions Permalink
  • monogrant

    Does the expiration feature need to be enabled globally?

     

    I'm trying to add expiration through the CLI and having no luck. We were getting `400 Bad Request` when we did not include role, but now with role added we're not getting anything. It just sits there.

     

    box collaborations:update --as-user=USER_ID COLLABORATION_ID -r=viewer --expires-at="2019-12-10T12:35:29-08:00"
    0
    Comment actions Permalink

Please sign in to leave a comment.