Complete REST API
Read and write on products, visuals, projects, stock and movements. Filtering, sorting and pagination on every field.
A visual platform is only useful if it fits into the existing information system. Everything the interface shows is reachable through the REST API, and recurring exchanges — ERP feeds, FTP drops with your suppliers, authentication against your corporate directory — are automated once and for all.
The API is not a grudging subset: it exposes the same scope as the interface, with the same permissions.
Read and write on products, visuals, projects, stock and movements. Filtering, sorting and pagination on every field.
Documentation is built into the platform: your developers read, test and replay calls from their browser, with nothing to install.
One key per user, revocable at any time, bound to exactly the same rights as the interface. No all-powerful service account.
Out-of-order updates are refused automatically: stale data cannot overwrite fresher data.
ERP feed for products, FTP / SFTP drops and pickups with your suppliers, authentication against your corporate directory, scheduled jobs.
Integrations specific to a trade or to a partner are developed by the publisher and deployed on your instance.
Each user generates their own key from their account. It inherits their rights and is revoked in one gesture, without touching the other integrations.
The interactive documentation lists resources, fields, filters and return codes. Calls are tested straight from the browser.
Products from the ERP, files to and from supplier FTPs, authentication against the directory, scheduled jobs: whatever repeats gets automated.
A need specific to your trade or to a partner? The integration is developed and deployed on your dedicated instance.
Technical openness is often what decides whether a platform is adopted beyond the studio.
Opening the API and the standard connectors (ERP feed, FTP / SFTP, corporate directory, scheduled jobs) are part of the product. Only integrations specific to a trade or to a partner require dedicated development.
By a key belonging to each user, revocable at any time. The key is bound to the same rights as the interface: it never reaches anything the user would not see on screen.
Yes. The interactive documentation is built into the platform: your developers test calls from their browser, with their own key, before writing a single line of code.
Yes, corporate directory authentication is one of the available connectors. Users sign in with the credentials they already have.
A visual's journey from request to delivery: workflows, guidelines, annotation, arbitration.
Learn more → ModuleOne product record, all its references, its visuals and its stock.
Learn more → ModuleThe library of every approved visual, with its history and its usage rights.
Learn more →Leave us your details: we will show you the application on your own media, and get back to you within one working day.
Thank you …, our team will get back to you shortly to arrange your demo.