While Threekit's Introduction: Client Side APIs are powerful ways to facilitate configuration & interactivity in a 3D space, the REST APIs will allow you to interact directly with the Threekit platform to create tools/utilities, robust integrations, and more.
The following is a brief explanation of the purpose for each server-side API.
The purpose of the analytics service is to capture session information of a user interacting with Threekit configurators/viewers. Customers can access raw analytics data from Threekit for use in their Business Intelligence solutions.
Used for importing and exporting assets to/from the platform. For importing, used in conjunction with the Files API.
This is the data model to store all of the Assets that exist in your org; Items, Models, Materials, Textures, etc.
Used for retrieving a list containing all item data from all items matching your specified query accessible by the authentication token used. Can be useful for mapping item names to item Ids when using the Configurator API.
Used for saving and accessing saved configurations. It is used by the sharing function to resume the configurator state.
Allows for tracking of where an order is being placed related to a specific platform.
Used for uploading and retrieving files to/from the Threekit Platform CDN. Main usage from an implementation standpoint is for uploading assets into an organization in conjunction with the Asset API.
The underlying Jobs system.
The layers service is a way to keep track of renders and exports of specific assets and their configurations. For example if there is an asset with 10 different configurations, it is not ideal to generate a render for all 10 configurations every single time a render job is triggered. Generate it once, make sure it is stored in layer-service, and just call the layer service to fetch that particular file.
This API is designed to be used by connectors, for example, Shopify integration. If an order is placed in an app like Shopify, those order details should also be stored in our database.
Used for importing and updating items, along with all their metadata, into the platform using JSON format. Can be used for updating multiple items that match the criteria defined in the query object. Also used to update configuration attributes and rules.
Webhooks can be used to trigger a number of things in the platform on the basis of some event.