Ganister is the first “API-first” solution for digitizing product lifecycle management. This is it, very simple, by design we decided to build our API before anything else. It means, we had to build all our technical (playing with nodes) and functional (playing with parts and documents) tests on this API. We had to focus on security, performances but also ease of access.
A functional API
The functional API gives you the power to communicate with the API in business terms. You don’t want to always use technical names, like nodes and items,etc… to query a document. You want to query a document, you want to get a full BOM, you want to have an Engineering change request impact analysis. We get close to business best practices within the API, way before thinking about a web User Experience.
A Technical API
We can’t cover every one’s business specificity. So we give freedom to extend the digitization of your business processes with Ganister by using more technical API at first. Create, query,update nodes, and you have a world of possibilities for digitizing any process.
A documented API
This is a key aspect. We hear sometime that developers don’t like documentation. Well the only true statement is that they don’t like writing things that could be automated. Updating a word document… yikes ! Most of the technical description of the API generates a documentation that is actually actionnable. You can test it directly in the documentation.
There must be a lot more to say about API, and we’ll let you discover all that, in our training or just by yourself during a trial period or as a customer.