eyebase APIs for read and write access
The eyebase API provides both read and write functionality, and a secure and standardized way for other applications to work with eyebase and deliver the information or functionality requested without user intervention.
The write API allows you to write a single asset record or multiple records to the eyebase solution. A related file can contain the metadata of the digital asset being imported. The associated XML metadata file will automatically be linked to the asset file. For example, as a flower.tif file is processed, eyebase will look for a corresponding flower.xml file. The automated processing of both files provides a complete record in eyebase.
A profile for the API write functionality defines what processes might run when data is being written. Examples of profile processes might be the assigning of pre-defined keywords, folder destination, or generating derivative versions.
New data records can also be read from a CSV file. The CSV file requires an entity ID column and an identifier for the type of data to write (eg images, documents, video, etc.), and any other fields such as title, description, and keywords.
The API read functionality provides access from a URL. Authentication is required. The read API retrieves the requested data and and returns the data in a useable format such as XML. The read API is typically used for sharing data with a third party, integrating with another application, embedding a piece of content, or integrating with internal systems.