I am looking for a complete online reference for iManage's latest API. On googling, can see references to iManage v2 documentation, but that seems to be bit old and where can I find latest API if at all there is one
The latest version which is constantly updated is available at https://help.imanage.com/hc/en-us/sections/360000214214-iManage-Work-REST-API-Documentation - you'll need a login to IManage's support site to access this though. If you don't have credentials you can raise a ticket with your support provider to get access.
If you have an on premises server that's licenced for the API, you'll find the documentation for that specific version at https://YOURSERVERNAME/api-docs/
iManage has 3 different versions of API's
COM API > This is a legacy classic api which is reaching EOL on Dec 2023. So it is not recommended any more.
REST API v1.0 > EOL already reached (Dec 2022)
If you're on-prem technically you can use REST API 1.0 till iManage Work 10.4.4 (but please validate) but you will not have any support from iManage in case of any issues
REST API 2.0 (also called iManage Universal API)
This is the latest version and going forward you need to use this version. And if I am not wrong this is supported from iManage Work 10.2.3.
You can find latest documentation at iManage Universal API 2.0
Or you can find your Work server specific documentation https://YOURSERVERNAME/api-docs/ (Provided you entered API license while installing iManage Work software)
Related
There are no samples on how to secure Azure Functions v4 with Azure B2C authentication.
There are some work arounds such as this for v3 and this one for v4 but it uses a really version of Microsoft.Identity.Web V1.5.1, saying that later ones are not supported. The latest version is 1.25.10.
Any docs online are complex and I could not get them working for the latest versions of everything. Is this something that Microsoft actuall supports of does anyone have a working example.
Newbie to API consumption and wasted hours trying to consume a REST 2.0 API resource to find out that we are using 1.0 API. Want to avoid this mistake in the future and looking for ways to identify API version that’s consumable.
In this case it’s an on-prem bitbucket server. Been searching if there’s any default ways to identify an applications API version without success.
Is there a good and easy way to identify which api version an application is accessible by?
No, I don't believe there is a general way APIs commonly use to communicate their versions
I have added Dropbox support to my apps a while ago and never touched the implementation since. It is still running fine. However, a few month ago Dropbox updated the way permissions are handled which may require code changed in my apps. As explained by Dropbox I have to check if my apps work with short-lived access tokens.
The Dropbox docs describe the necessary changes when using their API directly but I use different versions of their official SDK in my apps:
iOS: ObjectiveDropboxOfficial 3.1.2
macOS: ObjectiveDropboxOfficial 2.0.6
Android: dropbox-core-sdk 3.0.6
As said, I have not changed or updated the Dropbox code in my Apps for a while. Newer versions of the SDKs are available and I will update them soon. However, I am not sure how to test, if the existing versions of my apps, using these SDK version support short-lived access tokens or not. How can I test this?
I have only configured the SDK code (provided the API key, etc.) and all API calls, tokens, etc. are handled by the SDK. How do I find out, if these SDK version work correctly work with the updated API?
The official Dropbox SDKs have been updated to support short-lived access tokens, as of v5.0.2 for the Dropbox Objective-C SDK, and v3.1.0 for the Dropbox Java SDK.
You should update to the latest versions and then update your code to use the latest methods for the authorization flow as covered here for the Objective-C SDK and here for using the Java SDK in an Android app.
Once you've done so, you should test the full app authorization flow by signing out and signing back in again, in each version of the app, along with whatever other testing you would normally do.
We have solution based product which expose the rest API and our product has quarterly releases. Also, we expose an API for all the functionality we do in UI, and it may by around 30 end point.
Current we are exposing the API as v1.0 for first release planned on this Month.
My Question regarding this API versioning are,
Do we need to increase an API version whenever there is new set of API released?
Do we need to support all old API in new version if new version get release?
Ex: We have AddUser API in v1.0, if we release AddUserWithoutEmail API in v2.0 then Do we need allow AddUser API in v2.0
I am aware that there is many Q&A available on this topic but I didn’t get what I am exactly looking for so I have created this one.
We are trying to migrate the API manager from 2.0 to 2.5.
followed the instructions from the WSO2 Documentation.
After the migration we are have strange issues
1. No download wsdl link for the API's shown in Store (Though publisher shows)
2. Static never expiry tokens are also not visible in store(Though publisher shows)
https://docs.wso2.com/display/AM260/Removing+Unused+Tokens+from+the+Database#RemovingUnusedTokensfromtheDatabase-ConfiguringAPIManagerfortokencleanup
This documentation fixed the issue.