while going through the history Api of html5, i got confused. What's the exact difference between router and history api. I mean if we consider the case of react-router, we can use history api also to change the url and load the content. Any help will be appreciated.
Related
We are currently looking into the monitoring of documents and activities in BIM360. Webhooks for version added or changed work to a certain extent but only capture so much.
There is a way to manually export the logs into a csv file and idealy we would want to automate this process so our BI department has data to work with.
Furthermore if not possible, is this something you guys are planning to add to the API in the near future or is it a low prio kinda thing.
Cheers and thanks in advance
Sorry we don't have a direct API to extract that information. There is a built-in UI feature.
Via API you can get each file's version history, but that would require a recursive function to craw all folders & subfolders.
Does anyone (you know who you are) know exactly what is disappearing when Autodesk deprecates the /v1 equivalent of the ModelDerivative API?
I've taken care of everything that was in the blog post here:
https://forge.autodesk.com/cloud_and_mobile/2016/09/autodesk-forge-apis-migrating-from-v1-to-v2.html
But I also have some calls such as:
/viewingservice/v1/:URN/status
and:
/viewingservice/v1/items/:dbpath object_ids.json.gz
That were not specifically mentioned. Will these also need to be modified?
These endpoints will no longer be valid. The status of a translation can be obtained by using the GET :urn/manifest endpoint.
We have official SDK's for multiple programming languages that will make it easier to handle the REST calls.
To download the derivatives of a model, the SDK's do not expose direct methods so you actually have to issue the calls "directly". Take a look at the extract.io sample that expose the full download workflow, more specifically there.
Hope that helps
Few days ago I was able to make request to:
https://drive.google.com/a/{{domain}}/file/d/{{docDriveId}}/image?pagenumber=1&w=400
Via this API I was able to get image preview on multi-page documents.
Seems it's there, but times-out after some time. It doesn't work anymore. Does anyone know what happened? It seems there's no documentation on this API.
On the other hand, I am aware of the thumbnailLink URL when getting document object via API, but this will only get 1st page preview.
Any alternative solutions to this?
Thanks a lot,
M
That URL is not a part of the official Drive API and is not guaranteed to remain stable. The Drive API doesn't include the ability to fetch per-page image previews of documents, but you may want to investigate using the embedLink as an alternative: https://developers.google.com/drive/v2/reference/files
I am trying to using Box API to get comments that have been made on the files and folders.
I have tried looking at the box content api but could not find anything useful. Am I missing something here?
AS is usually the case it turns out I was not digging real deeply into the documentation.
Here is the link to the documentation for accessing comments in the box.com api.
https://developers.box.com/docs/#comments
The link explains it really well. I cant really think of copying and pasting it here since I wont be adding anything. The key concept in box.com api is the authentication and after that one can simply pass parameters for file_id and then post and go to /comments url and get the response. Then comes the sifting of comments which can also be done using the api.
With the somewhat recent update to the Twitter API, links for JSON pages don't seem to work anymore. I'm wondering how I can get a link similar to this one: http://search.twitter.com/search.json?q=apple (which would find tweets about apple). This link is broken (as you'll see if you click on it).
Yes your link is deprecated now, the link would be like this for api v1.1:
https://api.twitter.com/1.1/search/tweets.json?q=apple
PS: You will need to create an account then authorize your application.
The Twitter oauth API V1 is deprecated completely as of late June. You need to change your code API V1.1 which allows you to view the content in the json file via authentication only.
Like #meda said, you need to have an application to run it with.
Once creating an application at twitter, you can use any twitter oauth library to collect the data from the json files.
ASFIK,https://github.com/abraham/twitteroauth [Abraham's twitter oauth] is the best for starters to learn the flow of authentication and easy access of twitter informations.