Creating A BOX shareable link via Fusion

[OmahaOmaha]

Has anyone ever created a shareable link to a Box file via fusion before?

[IvanBebek-iX]

Hi @OmahaOmaha,

Could you please elaborate on how do you see this functionality working, that you have a workfront fusion link that would download the file, preview the file or something else?

Maybe write it in a way

• What have you done by now?
• How do you expect this to work?
• What are current limitations you noticed?
• Do files only live in Box or are they available in Workfront also?

Thank you in advance.

Best regards,
Ivan

[OmahaOmaha]

Sure, I have a scenario that uploads files to box. I trying to create another scenario that makes a shareable link for that BOX file, so  that I can then share the file with users who do not have access to our instance of BOX.

Currently I'm attempting to use the BOX make API call module to pull this off:

URL: /files/{{55.`DE:BOX Document ID`}}/shared_links

Body: {
"access": "open",
"permissions": {
"can_download": true,
"can_preview": true
}
}

but this errors out when I run it.

[IvanBebek-iX]

Hi @OmahaOmaha ,

After a bit of digging it seems that the URL that you have in the Workfront module is incorrect, per official Box documentation https://developer.box.com/reference/put-files-id--add-shared-link/ it should be a PUT request with

/files/{{55.`DE:BOX Document ID`}}?fields=shared_link

and the body per some examples can be found 

{
  "shared_link": {
    "access": "open",
    "password": "do-not-use-this-password", 
    "unshared_at": "2022-12-12T10:53:43-08:00",
    "vanity_name": "my-shared-link",
    "permissions": {
	  "can_view": true,
	  "can_download": true,
	  "can_edit": true
    }
  }
}

also for the details on each field please check https://developer.box.com/reference/put-files-id--add-shared-link/#body-parameters and adapt the request to your needs.

Hopefully this helps.

Best regards,
Ivan 

[OmahaOmaha]

@IvanBebek-iX I entered the body and link you provided, but I'm still getting a [404] (error code: ) when testing out the module.  Do you know why that might be?

[IvanBebek-iX · Accepted solution]

Hi @OmahaOmaha ,

I was looking at the Box documentation and this is how it should be, did you follow all of the steps with creating dev acc and proper auth and everything https://daily.dev/blog/box-developer-documentation-getting-started maybe check this link? This blog contains all of the relevant informations, please let me know if you still have problems after following the steps mentioned.

Thank you in advance.

Best regards,

Ivan

[kautuk_sahni]

@OmahaOmaha Just checking in! Were you able to get this resolved? If you found your own solution, sharing the details would be a big help to others who might face the same issue later on. And if one of the replies here helped, whether it fully solved the problem or simply pointed you in the right direction, marking it as accepted makes it much easier for future readers to find. Thanks again for helping close the loop and contributing to the community!