Extending The Initiative API For Better Transforma...

This is an important step toward connecting transformation initiatives more effectively with the tools teams already use, while staying aligned with the broader direction of the core asset model.

In many cases, transformation work spans multiple systems: deliverables may be tracked in Jira, architecture context maintained in LeanIX, objectives managed in OKR platforms, and execution supported through tools such as SAP Cloud ALM. Keeping these elements aligned manually can create additional coordination effort and data inconsistency.

With this API extension, teams can establish and manage links between initiatives and related assets more systematically. This helps keep transformation data connected across systems and reduces the manual effort required to maintain consistency.

The API extension supports working with assets related to initiatives and provides the foundation for broader integration scenarios across the transformation management ecosystem.

Why This Matters

Your transformation initiatives don't live in isolation—your tooling shouldn't either.

Enterprise transformation initiatives are complicated endeavors. For instance, there could be process models created within Signavio, development activities managed in Jira, architectures defined within LeanIX, and OKRs tracked in some other platform. BeforePrior to today, keeping the integration between these initiatives was only possible through either manual work that did not scale well, or through fragile point-to-point integrations that broke constantly.

The Assets API provides a means of ensuring that the initiative context remains accurate and complete through an officially supported mechanism. Third parties can develop packaged solutions for connecting SAP Signavio Process Transformation Manager with various systems. The same applies to internal teams which would like to automate their workflows.

The current API extension provides a foundation for working with initiative-related assets. Further coverage and capabilities can be expanded based on integration use cases and alignment with the core asset model.

17 Asset Types Ready for Your Workflows

Category	Asset Types	Use Case Examples
Analytics	METRICS, DASHBOARD, INVESTIGATION	Link KPI dashboards and process mining investigations.
Process	PROCESS_MODEL, PROCESS_FLOW, IMPROVEMENT_OPPORTUNITY	Connect process models and identifiyed improvements.
Project Management	JIRA, TASK, BLOCKER	Track implementation work and blockers.
Strategy	OBJECTIVE, KEY_RESULT	Align with OKRs and strategic objectives.
External Systems	LEANIX, SAP_CLOUD_ALM	Integrate enterprise architecture and cloud projects.
Documents	DOCUMENT, FILE	Attach project charters, specifications, reports.
Other	CORRECTION_RECOMMENDATION, OTHER	Custom and specialized asset types.

Five Endpoints, Full Control

All Assets API endpoints are nested under the Initiatives resource:

1. List Assets in Initiative

GET /transformationmanager/v1/initiatives/{initiativeId}/assets

Retrieves all assets linked to a specific initiative.

2. Create Asset for an Initiative

POST /transformationmanager/v1/initiatives/{initiativeId}/assets

Request Body:

{ 
   "name": "Q2 Sprint Planning Board", 
   "description": "Jira board tracking implementation tasks", 
   "type": "JIRA", 
   "url": "https://jira.example.com/browse/TRANSFORM-123" 
}

Response: 201 Created with the full asset object.

3. Get specific Asset within an Initiative

GET /transformationmanager/v1/initiatives/{initiativeId}/assets/{assetId}

4. Update specific Asset within an Initiative

PUT /transformationmanager/v1/initiatives/{initiativeId}/assets/{assetId}

5. Delete Asset within an Initiative

DELETE /transformationmanager/v1/initiatives/{initiativeId}/assets/{assetId}

6. Asset Object Structure

{ 
   "id": "550e8400-e29b-41d4-a716-446655440000", 
   "name": "Q2 Sprint Planning Board", 
   "description": "Jira board tracking implementation tasks", 
   "type": "JIRA", 
   "url": "https://jira.example.com/browse/TRANSFORM-123", 
   "initiative": { 
     "id": "3f017a39-884c-49f2-b6ee-51ce0ee5122f", 
     "name": "Order-to-Cash Automation" 
   }, 
   "createdBy": { 
     "id": "user-uuid", 
     "displayName": "Jane Smith" 
   }, 
   "updatedBy": null, 
   "dateCreated": "2026-04-17T10:30:00Z", 
   "dateUpdated": null 
}

Required fields for create/update: name, type, url
Optional: description

Secure Access with JWT Bearer Tokens

The Assets API uses the same authentication as other SAP Signavio Process Transformation Manager APIs (see further details at SAP Help )

Obtain a Bearer Token from /auth/v1/token
Include the token in the Authorization header:

Authorization: Bearer

Tokens are valid for 8 hours.

Your First Integration in 15 Minutes

Use Case 1: Automated Initiative Setup

When creating a new transformation initiative, automatically link relevant resources from Jira, LeanIX, and SharePoint.

Use Case 2: Cross-Tool Reporting

Pull all initiative assets to create unified transformation reports that aggregate Jira items, dashboards, and documents.

Use Case 3: OKR Synchronization

Sync objectives and key results between your OKR platform and initiative assets for real-time strategic alignment.

Resources

For Developers

Ready to Get Started?

Ready to connect your first asset programmatically?

Start with something simple: link a Jira epic to an existing initiative using the Create endpoint. It takes about 15 minutes from reading this post to seeing your first asset appear in Transformation Manager. From there, you can expand to automated syncs, bi-directional updates, or full dashboard integrations.

The API is live. Your transformation initiatives are waiting. Let's connect them.

Have questions or want to share what you're building? Drop a comment below or connect with me on the SAP Community—I'd love to hear how you're putting this to work.

Source link