Switch to asynchronous processing of the SBOM file ingestions

With an enhancement to our REST API, we'll future-proof the ingestions of SBOM files for self-build software discovery. Switching to asynchronous API call processing will build the foundation for additional post-processing mechanisms and scalability. Although there is no established timeline for future API extensions, we aspire to have the technical foundation ready.

Predictions show that the traffic on the API endpoint will increase to a point where its synchronous processing impacts performance and service reliability. In this regard, introducing asynchronous processing of the SBOM files will ensure the API's continuous service stability.

From April 7, 2025, the API will return a new HTTP 202 (accepted) status code in responses and contain additional payload fields. This status indicates that the request has been accepted for processing but has not been completed. While the SBOM file's processing will be asynchronous, the request payload validation will remain immediately upon API request. Please update your integrations to this endpoint to recognize the changes in response.

You can try out the new API behavior from today by calling the existing API with the header x-leanix-dev set to dev. Our developer documentation provides further details with response code and payload examples.