Unable to Retrieve Collaborator Email Address for a non-Registered Collaborator
From the Developer:
Steps to reproduce:
1) Create a collaboration to a folder with email, that not already registered in Box.com.
2) Create a request via Java SDK to get collaborations from this folder. Response like this will be returned:
{"totalcount":1,"entries":[
{"type":"collaboration",
"id":"987654321",
"createdby":{"type":"user","id":"23421234","name":"xxx","login":"xxx@xxx.xxx"},
"createdat":"2016-09-05T07:18:42-07:00",
"modifiedat":"2016-09-05T07:18:42-07:00",
"expiresat":null,
"status":"pending",
"accessibleby":null,
"role":"editor",
"acknowledgedat":null,
"item":{"type":"folder","id":"123456","sequenceid":"0","etag":"0","name":"FolderToCollaborate"}}
]}
'AccessibleBy' is null. So we don't receive an information about collaboration, for example email. But if user with this email registered in box, we receive information about it, like this:
...
"status":"accepted",
"accessible_by":{"type":"user","id":"1233445678","name":"Yyy .","login":"yyy@yyy.yyy"},
"role":"viewer",
...
If we need to create a collaboration, we need at least to know a login of collaborated user even it not registered in box.
Our system (cloudally.com) creates a backups of all chosen box.com account files and folders. So, when we backup folders, we collect information about collaborations too. Then we restore it via java sdk. And due to the above we can't restore collaborations with users that not already registered.

The accessible_by field now returns email addresses of unregistered collaborators.
-
Franklin commented
Totally agree. Knowing of a pending status is 1/2 baked without knowing who you are pending for. Identification of who's pending would be really helpful to complete this delivery.