-
-
Re: API v3 and Secret/Private groups
Hey Mark,
Just direct through the API, using a RESTClient in Chrome.
I'm able to interact with all other groups (I can retrieve via GET).
-
Re: API v3 and Secret/Private groups
Is the user you've used to authenticate with the V3 API a member of the secret group or a full-Access Admin?
-
Re: API v3 and Secret/Private groups
Yes, I'm logged in as the owner of the first group I'm testing, and I'm a full admin of the other.
-
Re: API v3 and Secret/Private groups
Would you be able to share the code, e.g. the app.xml (preferred) or the osapi call that you are trying?
-
Re: API v3 and Secret/Private groups
Hi Mark,
I'm not using any code. I'm going for a simple approach using a Chrome REST client: https://chrome.google.com/webstore/detail/hgmloofddffdnphfgcellkdfbfbjeloo
I'm doing a GET request on places. I'm able to get back information just fine for groups that aren't secret or private. As soon as I try the same call against a secret group that I'm the owner of, I get the error message I posted above.
-
-
-
-
-
-
Re: API v3 and Secret/Private groups
craig.mcclanahan
Apr 18, 2013 1:32 PM
How are you composing the URI that you are using (https://urbanairship.jiveon.com/api/core/v3/places/1089)? If you are assuming that you can use the "id" field from the group, that is not going to work. The right URI to use for a place is the one in the "self" resources link.
Beyond that, you won't be able to retrieve a secret group at all unless you are an administrator or member of that group. You will be able to retrieve a private group whether or not you are a member (although you will not be able to retrieve any content from it).
-
Re: API v3 and Secret/Private groups
2 people found this helpfulCraig, here's the way I was able to find the right "self" resources link:
https://community.jivesoftware.com/api/core/v3/search/places?filter=search(MYGROUPNAME)&type=(place)
What's the best way to find the self URI resource in the future? Is my above REST call the ideal way?
Thank you for solving my problem.
-
Re: API v3 and Secret/Private groups
1 person found this helpfulHi Guys,
Put an internal ID in parallel of an common ID, this one easy to find, and makes all possible in the world to hide it... And base requests on it...
Someone at Jive want to see the world burn!
Put this tips on the documentation could be great. Instead of just talk about URI without mentionning the way to find it...
THANK YOU, you have saved me!
Guillaume
-
Re: API v3 and Secret/Private groups
Another way that I use (since I come from a Plugin paradigm) is this call:
/api/core/v3/contents?filter=entityDescriptor(102,1002)
In this case, 102 = Document and 1002 is the ID I see in the URL etc... This payload returns me the object in question with the self URI link.
Obviously, the IDs can be switched out to be what ever ... 700 for Social Group, 600 for Project, 14 for Space, 1 for Discussion, 38 for Blog Post, etc...
Update: You will need to use /places instead of /contents for places in the above example.
-
Re: API v3 and Secret/Private groups
Ah that's handy to know, it's been a right pain to keep looking up the placeID - incidentally, why doesn't the API return the placeID in an easily accessible field?
-
-
-
-