SAP Integration Content API - Is it possible to view all process direct endpoint value

[jbesl99]

Hello Experts, 

I was exploring the available Integration Content API - https://api.sap.com/api/IntegrationContent/overview, 

to view existing data of deployed package/iflows from our SAP CPI. But couldn't find an API which will extract all values of all process direct adapters of deployed artifact / iflows. Is this API feature available?

I have this requirement to extract this data to document all the endpoints to build a detailed landscape of integrations. Since we are using an Async Pipepline, and uses an interface routing iflow which points the received idoc to multiple process direct destination. Need to identify the which iflow the process direct endpoint is used.

@

[FrankW]

Hi!

I need the same functionality: a list of all ProcessDirect endpoints alongside their corresponding iFlow names. Did you find a solution to your problem? Unfortunately, the /ServiceEndpoints API doesn't provide ProcessDirect endpoints. From my perspective, you could do the following:

• Get all packages with the /IntegrationPackages API.
• For each package, retrieve the list of all artefacts: /IntegrationPackages('MyPackage')/IntegrationDesignTimeArtifacts.
• For each iFlow artefact, download the content: /IntegrationDesignTimeArtifacts(Id="MyIFlow", Version="active")/$value.
• Unzip the content and read the file: src/main/resources/parameters.propdef.
• Select all entries from the node: <param_references> where the attribute_id contains ProcessDirect.

<param_references> where the attribute_id contains ProcessDirect.
<reference attribute_category="Sender1" attribute_id="ctype::Adapter/cname::ProcessDirect/vendor::SAP/version::1.1.2/attrId::address" attribute_uilabel="Address" param_key="address"/>​

• You can fetch the endpoint, which relates to the attribute param_key, from the file: src/main/resources/parameters.prop.

#
Tue Sep 09 13:24:51 UTC 2025 
address=/myEndpoint
​

• Alternatively, use the API /IntegrationDesignTimeArtifacts(Id="MyIFlow",Version="active")/Configurations and search for the parameter key with the same value as param_key.

"ParameterKey": "address",
"ParameterValue": "/myEndpoint",​

I could not find an easier solution.

[brooksamanda]

That’s a great question and a pretty common challenge when documenting complex CPI landscapes. Unfortunately, the Integration Content API doesn’t expose process direct endpoint values directly, since those are handled at design-time within the artifact and not stored as runtime metadata.

One workaround I’ve seen is exporting the integration packages (via Design APIs or manual export) and parsing the *.iflow descriptor files. You can extract the process direct adapter configuration XML and map endpoint names to flows programmatically. It’s not elegant, but it gives a full inventory when you need to visualize inter-flow dependencies.

If your goal is to maintain an integration landscape view, you might also consider automating metadata extraction periodically to track changes in endpoints, it helps a lot when new iflows are deployed or versions change.

Would be interested to hear if anyone’s found a more direct API-based approach recently.