I know that there is available &limit parameter for /feed endpoint. However, on it's documentation page, it is nowhere mentioned that there exists limit parameter:
https://developers.facebook.com/docs/graph-api/reference/v3.0/page/feed
How i should have known that? Where I can see what other parameters are available for query?
Before hitting the reference, you should check out the general docs:
https://developers.facebook.com/docs/graph-api/using-graph-api/
It´s like a "getting started" article, useful for every developer.
Related
Currently, the Google Vault API does not provide a way to get a report of all users in a G-Suite tenant or domain who are on hold in one or more matters. This information is currently available only via the admin interface for Google Vault under Reports/User Holds. It would be great to be able to obtain this report via an API call in JSON format rather than only via the admin UI. Am I missing something or is this functionality already available?
Respectfully, please keep in mind that suggesting that I perform API operations to search all matters and iterate through the users on hold in each matter to obtain this information is not the answer I am looking for. There should be a quicker, more efficient way to get this information since such a report is already available via the UI. I am simply asking if there is a way to get this same information programmatically via the APIs/automation. Thank you in advance.
Unfortunately, Vault API does not have a method for that. The only way to retrieve this information is to list all matters and iterate through them, as you already mentioned.
File a feature request:
It's not uncommon for a feature to be present only in the UI. If you want to see this implemented on the API, I'd suggest you to report it on Issue Tracker's Vault component.
I looked through the issues of this component, and it looks like this hasn't been requested yet. There's currently a somewhat related feature request, but not exactly what you're looking for:
Audit reporting functionality
Update:
The original poster filed a feature request in Issue Tracker. I'm add this to the answer in order to give it more visibility.
To anyone who would like to see this feature implemented in the future, I'd suggest starring the issue (star on the top-left) in order to help prioritizing it:
Vault API: Need API method to return list of all users who have active holds as available in Vault UI
While researching I found that it's possible to research things on facebook using the /search path. However I cannot find any documentations on how to use this functionality.
I already know that the graph api documentation is https://developers.facebook.com/docs/graph-api
I already looked at the places search documentation at https://developers.facebook.com/docs/places/search
Nevertheless, what I would like to know is all parameters that I can use for the graph.facebook.com/search
For the moment I know that I can use q, and type with user,page, or group.
Where I should look for the complete documentation about this path?
Edit: Solved
Look at the comment by CBroe 13
It looks like Facebook has recently removed the documentation for this, maybe temporary, and probably because of recent "privacy breaches". You can check out this older copy on https://web.archive.org/web/20170104062957/https://developers.facebook.com/docs/graph-api/using-graph-api/#search – CBroe 13 hours ago
Per
https://developers.facebook.com/blog/post/2018/04/04/facebook-api-platform-product-changes/
Search API
Deprecated: Support for finding pages, groups, events, users using
search.
It's not deprecated, it's discontinued.
While they say it is "deprecated", it has been terminated and so far I have not found anything that speaks of a replacement. Here is another announcement:
https://developers.facebook.com/docs/graph-api/changelog/breaking-changes#search-4-4
FYI, I have posted a comment on the Facebook Developers Community page, hoping to elicit some kind of response from Facebook:
https://www.facebook.com/groups/fbdevelopers/permalink/1742432315800275/
You can find detailed Graph API documentation on the developers page
https://developers.facebook.com/docs/graph-api/using-graph-api/
Details about Search API is also available here.
https://developers.facebook.com/docs/places/search
Is the difference between having url parameters passed as
http://myserver/someoperation/bob/sally
versus
http://myserver/someoperation?arg1=bob&arg2=sally
purely up to user preference or are there good reasons for each?
I have a web service that is using the first style, but I am wondering if I am missing part of the equation.
As far as search engine optimization goes, Google has stated:
If your URL contains relevant words, this provides users and search engines with more information about the page than an ID or oddly named parameter would.
That seems to imply that having pages where your URLs have meaningful information would give your page a better ranking although they don't outright say that.
You can read more on their full guide: Google Search Engine Optimization Starter Guide (PDF). That quote was from page 8.
How can one change the opengraph link value on a Facebook page (type: website) from
https://www.facebook.com/yourwebsite to http://www.yourwebsite.com
It seems easier than it is. I couldn't find an answer. Seems it has something to do with adding an app, and then?!
Example: http://graph.facebook.com/anguillabeachescom
I can’t see that being done anywhere on the page’s settings interface.
My guess would be you have to claim your domain with Facebook to make things work this way (and maybe have to have a special category set for your Facebook page – the example page you mentioned is of type “website”.)
Has Facebook ever provided a way to ascertain when a page was created either through the Graph API, the Legacy API, or FQL? I can't seem to find it.
No, the creation date of a page isn't exposed anywhere in the API
According to this offical resource :
https://developers.facebook.com/docs/reference/fql/page
There is no any column that mention about the time when page is created.