No, not really. But the API itself is quite simple, to get current sharing information, you just do:
/api/sharing/type=dashboard&id=ID (GET request)
and then to update, you can use (PUT/POST request):
/api/sharing/type=dashboard&id=ID
With your JSON payload
It’s probably easiest to just sniff on the POST with web inspector, and you will get an idea of the API, for example I set external, added a group, and set public read on a dashboard on our test server, and the resulting JSON was:
{
“meta”: {
“allowPublicAccess”: true,
“allowExternalAccess”: true
},
“object”: {
“id”: “iMnYyBfSxmM”,
“name”: “Delivery”,
“publicAccess”: “r-------”,
“externalAccess”: true,
“user”: {
“id”: “GOLswS44mh8”,
“name”: “Tom Wakiki”
},
“userGroupAccesses”: [
{
“id”: “wl5cDMuUhmF”,
“name”: “Administrators”,
“access”: “r-------”
}
]
}
}
The meta object you can just ignore, but the rest of the API should be clear enough.
Please write back if you need more information, I don’t think anyone else is using the sharing API, so there might be some rough edges.
On Fri, Aug 29, 2014 at 9:28 AM, Morten Olav Hansen mortenoh@gmail.com wrote:
No, not really. But the API itself is quite simple, to get current sharing information, you just do:
/api/sharing/type=dashboard&id=ID (GET request)
and then to update, you can use (PUT/POST request):
/api/sharing/type=dashboard&id=ID
With your JSON payload
It’s probably easiest to just sniff on the POST with web inspector, and you will get an idea of the API, for example I set external, added a group, and set public read on a dashboard on our test server, and the resulting JSON was:
{
“meta”: {
“allowPublicAccess”: true,
“allowExternalAccess”: true
},
“object”: {
“id”: “iMnYyBfSxmM”,
“name”: “Delivery”,
“publicAccess”: “r-------”,
“externalAccess”: true,
“user”: {
“id”: “GOLswS44mh8”,
“name”: “Tom Wakiki”
},
“userGroupAccesses”: [
{
“id”: “wl5cDMuUhmF”,
“name”: “Administrators”,
“access”: “r-------”
}
]
}
}
The meta object you can just ignore, but the rest of the API should be clear enough.
Please write back if you need more information, I don’t think anyone else is using the sharing API, so there might be some rough edges.
On Fri, Aug 29, 2014 at 9:28 AM, Morten Olav Hansen mortenoh@gmail.com wrote:
No, not really. But the API itself is quite simple, to get current sharing information, you just do:
/api/sharing/type=dashboard&id=ID (GET request)
and then to update, you can use (PUT/POST request):
/api/sharing/type=dashboard&id=ID
With your JSON payload
It’s probably easiest to just sniff on the POST with web inspector, and you will get an idea of the API, for example I set external, added a group, and set public read on a dashboard on our test server, and the resulting JSON was:
{
“meta”: {
“allowPublicAccess”: true,
“allowExternalAccess”: true
},
“object”: {
“id”: “iMnYyBfSxmM”,
“name”: “Delivery”,
“publicAccess”: “r-------”,
“externalAccess”: true,
“user”: {
“id”: “GOLswS44mh8”,
“name”: “Tom Wakiki”
},
“userGroupAccesses”: [
{
“id”: “wl5cDMuUhmF”,
“name”: “Administrators”,
“access”: “r-------”
}
]
}
}
The meta object you can just ignore, but the rest of the API should be clear enough.
Please write back if you need more information, I don’t think anyone else is using the sharing API, so there might be some rough edges.