Our customers are not limited by the iconik API. Developers can create extremely customized and creative solutions for their organizations by linking services and data from 3rd parties. Any task that can be done in the iconik UI can also be done through the iconik API.
Trigger iconik operations from your own code. This could be used to add, transfer, or archive files and a lot more.
Trigger your code with iconik events using webhooks. This could be when metadata is updated, a job fails, a file is deleted, or any other event that can take place in iconik.
Integrate iconik with 3rd party systems. This could be used to populate the metadata from a quality check integration point or a monetization tool.
Send your data back and forth between iconik and 3rd party systems. This could be used to send metadata values from iconik into an ads manager or sales and marketing tool.
We practice API-first development by planning the design of our data model and API’s before any code is written. To create the most dynamic tool possible, we built iconik on an API that is consistent and backward compatible. The result is a cloud-native media management solution that functions within an ecosystem of services.
The iconik development team uses the same open APIs that we make available to anyone—we hold nothing back.
Building on top of our API keeps the developer in focus. API-first development saves time and reduces work by laying down a foundation for others to build on top of. We continue to invest in the iconik API so our users can develop more in less time.
The thorough iconik documentation ensures that our API is easy to understand so other developers can build upon it.