Factory Lens exposes secure REST APIs that allow you to retrieve dependency and integration metadata from an OutSystems 11 factory.
It can be used to support:
Factory Lens exposes metadata such as:
All Factory Lens APIs are protected using an API key.
The API key must be sent in every request using the following HTTP header:
x-api-key: <your-api-key>
Requests without a valid API key will be rejected with:
401 UnauthorizedStep 1 — Generate an API keyGenerate a strong random API key.Example format:flens_<random-secure-token>Step 2 — Store the API key in Factory LensThe API key is configured in the FactoryLensAPI module using a Secret Site Property.In Service Center:Go to Factory.Open Modules.Search for:FactoryLensAPIOpen the module details.Go to Site Properties.Find the API key site property.Example name:FactoryLensAPIKeyor, if your implementation stores a hash:FactoryLensAPIKeyHashSet the value.Save the configuration.Because this is a Secret Site Property, the value is stored securely and should not be exposed in logs, screens, or API responses.Common API endpointsThe available endpoints may depend on the installed version of Factory Lens.Typical endpoints include:GET /FactoryLensAPI/rest/v1/dependencies/modules GET /FactoryLensAPI/rest/v1/dependencies/modules/details GET /FactoryLensAPI/rest/v1/integrations/rest/consumed GET /FactoryLensAPI/rest/v1/integrations/rest/exposed GET /FactoryLensAPI/rest/v1/integrations/soap/consumed GET /FactoryLensAPI/rest/v1/integrations/soap/exposed GET /FactoryLensAPI/rest/v1/integrationsExample with filters:GET /FactoryLensAPI/rest/v1/dependencies/modules?applicationName=Customer%20Portal&direction=BOTHExample integration query:GET /FactoryLensAPI/rest/v1/integrations?protocol=REST&direction=CONSUMEDMinimal setup checklistBefore using Factory Lens, confirm that:FactoryLensAPI is published. The API key Secret Site Property is configured. The API key is sent using the x-api-key header. The required System and Extended Metamodel entities are referenced. The dependency endpoints return data. The integration endpoints return data. Factory Lens Demo points to the correct API base URL.
401 Unauthorized
Generate a strong random API key.
Example format:
flens_<random-secure-token>
The API key is configured in the FactoryLensAPI module using a Secret Site Property.
In Service Center:
FactoryLensAPI
Example name:
FactoryLensAPIKey
or, if your implementation stores a hash:
FactoryLensAPIKeyHash
Because this is a Secret Site Property, the value is stored securely and should not be exposed in logs, screens, or API responses.
The available endpoints may depend on the installed version of Factory Lens.
Typical endpoints include:
GET /FactoryLensAPI/rest/v1/dependencies/modules GET /FactoryLensAPI/rest/v1/dependencies/modules/details GET /FactoryLensAPI/rest/v1/integrations/rest/consumed GET /FactoryLensAPI/rest/v1/integrations/rest/exposed GET /FactoryLensAPI/rest/v1/integrations/soap/consumed GET /FactoryLensAPI/rest/v1/integrations/soap/exposed GET /FactoryLensAPI/rest/v1/integrations
Example with filters:
GET /FactoryLensAPI/rest/v1/dependencies/modules?applicationName=Customer%20Portal&direction=BOTH
Example integration query:
GET /FactoryLensAPI/rest/v1/integrations?protocol=REST&direction=CONSUMEDMinimal setup checklistBefore using Factory Lens, confirm that:FactoryLensAPI is published. The API key Secret Site Property is configured. The API key is sent using the x-api-key header. The required System and Extended Metamodel entities are referenced. The dependency endpoints return data. The integration endpoints return data. Factory Lens Demo points to the correct API base URL.
GET /FactoryLensAPI/rest/v1/integrations?protocol=REST&direction=CONSUMED
Before using Factory Lens, confirm that:
FactoryLensAPI is published. The API key Secret Site Property is configured. The API key is sent using the x-api-key header. The required System and Extended Metamodel entities are referenced. The dependency endpoints return data. The integration endpoints return data. Factory Lens Demo points to the correct API base URL.
401 Unauthorized Step 1 — Generate an API keyGenerate a strong random API key.Example format:flens_<random-secure-token>Step 2 — Store the API key in Factory LensThe API key is configured in the FactoryLensAPI module using a Secret Site Property.In Service Center:Go to Factory.Open Modules.Search for:FactoryLensAPIOpen the module details.Go to Site Properties.Find the API key site property.Example name:FactoryLensAPIKeyor, if your implementation stores a hash:FactoryLensAPIKeyHashSet the value.Save the configuration.Because this is a Secret Site Property, the value is stored securely and should not be exposed in logs, screens, or API responses.Common API endpointsThe available endpoints may depend on the installed version of Factory Lens.Typical endpoints include:GET /FactoryLensAPI/rest/v1/dependencies/modules GET /FactoryLensAPI/rest/v1/dependencies/modules/details GET /FactoryLensAPI/rest/v1/integrations/rest/consumed GET /FactoryLensAPI/rest/v1/integrations/rest/exposed GET /FactoryLensAPI/rest/v1/integrations/soap/consumed GET /FactoryLensAPI/rest/v1/integrations/soap/exposed GET /FactoryLensAPI/rest/v1/integrationsExample with filters:GET /FactoryLensAPI/rest/v1/dependencies/modules?applicationName=Customer%20Portal&direction=BOTHExample integration query:GET /FactoryLensAPI/rest/v1/integrations?protocol=REST&direction=CONSUMED Minimal setup checklistBefore using Factory Lens, confirm that:FactoryLensAPI is published. The API key Secret Site Property is configured. The API key is sent using the x-api-key header. The required System and Extended Metamodel entities are referenced. The dependency endpoints return data. The integration endpoints return data. Factory Lens Demo points to the correct API base URL.
GET /FactoryLensAPI/rest/v1/integrations?protocol=REST&direction=CONSUMED Minimal setup checklistBefore using Factory Lens, confirm that:FactoryLensAPI is published. The API key Secret Site Property is configured. The API key is sent using the x-api-key header. The required System and Extended Metamodel entities are referenced. The dependency endpoints return data. The integration endpoints return data. Factory Lens Demo points to the correct API base URL.