Quick Start¶
For getting started with our Application and our APIs, kindly refer to Getting Started.
For general information about the Procurement functionality, refer to the respective section in the SiGREEN Help: Procurement made easy.
Concepts and Glossary¶
For detailed information about the concepts and terminology, please refer to Concepts and Glossary.
Procurement API¶
The Procurement API, part of SiGREEN's suite of APIs, offers a streamlined solution for managing component-level emissions within procurement processes. With various endpoints mentioned below, users can efficiently access and analyze crucial data related to components and suppliers.
Suppliers¶
Prerequisite: In order to create a supplier, it is mandatory to create the supplier identifier type first.
Getting started with the Procurement APIs involves the following steps with respect to the Suppliers:
Create a supplier identifier type for a company in SiGREEN. The identifier type created initially in the beginning acts as the main identifier type.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/suppliers/identifierTypes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data '{ "idType": "Supplier ID" }'
Example Response
{ "id": "0190832b-b69b-778f-a843-a2a787a0827d" }
Get supplier identifier types for a company in SiGREEN.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/suppliers/identifierTypes' \ --header 'Authorization: Bearer TOKEN' \
Example Response
{ "items": [ { "id": "0190832b-b69b-778f-a843-a2a787a0827d", "idType": "Supplier ID", "isMainIdentifierType": true } ], "hasNext": false, "hasPrev": false, "page": 0, "pageNumber": 1, "size": 1, "totalPages": 1 }
Create a supplier in SiGREEN.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/suppliers' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data-raw '{ "name": "Supplier Company Limited", "identifiers": [ { "idType": "Supplier ID", "value": "SUP-123", "default": true } ], "email": "demo@demo.com", "contactNumber": "+91 234-234-2445", "website": "www.demo.com", "locations": [ "12459 Berlin, Siemensstraße 42" ], "comment": "Proc Supplier" }'
Example Response
{ "id": "01908348-1ade-718b-9895-0b53c9e4a4f9" }
Get supplier details by ID for a company in SiGREEN.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/suppliers/01908348-1ade-718b-9895-0b53c9e4a4f9' \ --header 'Authorization: Bearer TOKEN' \ --data ''
Example Response
{ "id": "01908348-1ade-718b-9895-0b53c9e4a4f9", "name": "Supplier Company Limited", "identifiers": [ { "idType": "Supplier ID", "value": "SUP-123", "default": true } ], "email": "demo@demo.com", "contactNumber": "+49 911 2155- 4444", "website": "www.demo.com", "locations": [ "12459 Berlin, Siemensstraße 42" ], "comment": "Proc Supplier" }
With the other available Supplier APIs, you can perform the following operations:
- Update supplier identifier type for a company in SiGREEN.
- Update a supplier by supplier ID in SiGREEN.
- Get all suppliers for one company in SiGREEN.
- Delete an unused supplier identifier type for a company in SiGREEN.
For more information in detail about the Parameters, Request Body, and Responses refer to the API Reference under Procurement API(s).
Components¶
Prerequisite: In order to create a component, it is mandatory to create the component identifier type first.
Getting started with the Procurement APIs involves the following steps with respect to the Components:
Create a component identifier type for a company in SiGREEN. The identifier type created initially in the beginning acts as the main identifier type.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components/identifierTypes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data '{ "idType": "SKU" }'
Example Response
{ "id": "0190835f-f167-7a6c-b8ab-2d5cb2c1d7e8" }
Get component identifier types for a company in SiGREEN.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components/identifierTypes?size=1' \ --header 'Authorization: Bearer TOKEN' \
Example Response
{ "items": [ { "id": "0190835f-f167-7a6c-b8ab-2d5cb2c1d7e8", "idType": "SKU", "isMainIdentifierType": true } ], "hasNext": false, "hasPrev": false, "page": 0, "pageNumber": 1, "size": 1, "totalPages": 1 }
Create a component in SiGREEN.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data '{ "name": "Frames", "materialCategory": "Electronics", "unit": "piece", "weight": "3.5", "identifiers": [ { "idType": "SKU", "value": "FRM1234", "default": true } ] }'
Example Response
{ "id": "0190838b-4469-76fc-b4bc-414c71526f2f" }
Get component details by ID.
Example Request
curl --location --request GET 'https://app.sigreen.siemens.com/api/components/0190838b-4469-76fc-b4bc-414c71526f2f' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data ''
Example Response
{ "id": "0190838b-4469-76fc-b4bc-414c71526f2f", "name": "Frames", "materialCategory": "Electronics", "unit": "piece", "weight": "3.5", "identifiers": [ { "idType": "SKU", "value": "FRM1234", "default": true }, ] }
Create secondary data with component. Either totalInclBio or totalExclBio mandatory.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components/0190838b-4469-76fc-b4bc-414c71526f2f/secondaryData' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data-raw '{ "email": "abc@testing.com", "totalInclBio": 2.345, "totalExclBio": 0.0021, "quantity": 1, "validityPeriodStart": "2024-06-04T08:30:00.000Z", "region": "Europe", "comment": "No Comments", "fossil": "100", "biogenic": "200", "dLuc": "50", "landUse": "150", "aircraft": "0", "dataSource": "Database", "dataVerification": "Proxy data" }'
Example Response
{ "secondaryDataId": "0190839e-1255-753b-8c52-a3202978a983" }
Get component secondary data by secondary data ID.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components/0190838b-4469-76fc-b4bc-414c71526f2f/secondaryData/0190839e-1255-753b-8c52-a3202978a983' \ --header 'Authorization: Bearer TOKEN' \ --data ''
Example Response
{ "totalInclBio": "2.345", "totalExclBio": "0.0021", "quantity": "1.0", "dataSource": "Database", "dataVerification": "Proxy data", "region": "Europe", "validityPeriodStart": "2024-06-04 08:30:00.0", "comment": "No Comments", "fossil": "100", "biogenic": "200", "landUse": "150", "aircraft": "0", "secondaryDataId": "0190839e-1255-753b-8c52-a3202978a983", "dLuc": "50", "email": "abc@testing.com" }
Link suppliers and secondary data with component.
Example Request
curl --location 'https://app.sigreen.siemens.com/api/components/0190838b-4469-76fc-b4bc-414c71526f2f/linkSuppliers' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer TOKEN' \ --data '[ { "supplierId": "01908348-1ade-718b-9895-0b53c9e4a4f9", "supplierLocation": "12459 Berlin, Siemensstraße 42", "share": 100, "supplierProductId": "SUPCOMP1", "secondaryDataId": "018fe8a5-349f-7e94-8032-d57f9420e2a4" } ]'
Example Response
[ { "supplierLocation": "12459 Berlin, Siemensstraße 42", "share": "100.0", "supplierProductId": "SUPCOMP1", "supplierId": "01908348-1ade-718b-9895-0b53c9e4a4f9", "secondaryDataId": "018fe8a5-349f-7e94-8032-d57f9420e2a4" } ]
With the other available Component APIs, you can perform the following operations:
- Update a component identifier type for a company in SiGREEN.
- Get all components for one company in SiGREEN.
- Get all component secondary data for component in SiGREEN.
- Update component secondary data by secondary data ID.
- Get all linked suppliers with component.
- Get linked suppliers by componentSupplierLinkId with component.
- Update location/share/secondary data/supplier product ID by component supplier ID.
- Delete an unused component identifier type for a company in SiGREEN.
- Delete link between component and supplier. Deletion of records supports only soft delete.
For more information in detail about the Parameters, Request Body, and Responses refer to the API Reference under Procurement API(s).
Components PCF¶
With the available Components PCF APIs, you can perform the following operations:
- Get an aggregated export of a PCF of a component.
- Get an export of a PCF of a component.
- GET the PCF data for your components in SiGREEN.
For more information in detail about the Parameters, Request Body, and Responses refer to the API Reference under Procurement API(s).