The REST API is targeted at building custom Web applications, mobile apps, and HTML interfaces that use or display assets from Assets Server. Of course it can also be used for server-side languages such as PHP, .NET and Java / JSP.
All the previews provided by Assets Server are based on Web standards and can be used in Web browsers or on any Web-enabled mobile device.
Note: The Assets Server REST API does not always respect all of the official REST guidelines. When it diverts, it is always in the interest of making the API easier to use from HTML based Web browsers.
Log in requirement
Before being able to request information from Assets Server by using a GET request or make changes to the system through a POST request, a log in to Assets Server is required.
Logging in can be done by using the following APIs:
- The REST API - login. This API provides the process of logging users into the system. It authenticates the Web browser session and returns a CSRF token which can then be used for future POST requests.
- The REST API - API login. This API is typically used for external integrations, allows multiple sessions and an API User license. It cannot be used within Assets in the Web browser. It uses the /apilogin call which returns an authentication cookie which can then be used for future POST requests.
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
Please sign in to leave a comment.