Authentication and token retrieval endpoints.
Luminovo API (1.0.0)
This API uses data model versioning to ensure that the API is backwards compatible. The data model and the version is specified using the Accept header. For instance, Accept: application/api.luminovo.rfq-v1+json specifies that the API should use version 1 of the RfQ data model. Please pay attention to the specific endpoint description, for correct handling of the accept header. If no Accept header is provided, the API will throw an 404 error!
For all enum types in the API, it is mandatory to account for an "Unknown" case. This ensures that your code remains forward-compatible, as we may introduce new enum variants in the future. Example: Consider an enum Status with the variants Ok, Error. We may add a status Warning without further notice in the same data model version!
Components are the fundamental building blocks that make up electronic assemblies (PCBs, products, etc.). You can view components in Luminovo under the "Parts" tab. There are OffTheShelf and Custom components in order to get good data quality in Luminovo.
OffTheShelfare all electonic components which have a MPN and can be purchased from an electronic parts suppliers.Customare all other non-electronic components, such as screws, packaging materials, lables, etc. Also, custom are all electronic components which are not standartized and don't have an MPN.
A demand in Luminovo is a request for a specific quantity of electronic parts or assemblies that need to be delivered by a certain date. Demands are attached to assembies or components within Luminovo based on the internal part number. Demand upload is relevant for the users of the Source-to-contract Luminovo module.