{
  "info": {
    "_postman_id": "0d652ba1-b8e3-47ee-85cc-6bd0e04899ab",
    "name": "WHINT Integration Cockpit API v1.2.0",
    "description": "Professional API collection for WHINT Integration Cockpit with streamlined configuration and comprehensive request coverage.\n\n**SETUP (2 minutes)**\n1. Import this collection into Postman\n2. Set Variables (Collection → Variables tab):\n   • **WHINT_BASE_URL**: Your instance domain (e.g., your-instance.cfapps.eu10.hana.ondemand.com)\n   • No https:// or /api needed\n   • **BEARER_TOKEN**: Your access token from Integration Cockpit\n3. 19 requests run right away, 8 need an optional variable (see below)\n\n**OPTIONAL VARIABLES** (only set when needed):\n• **EXAMPLE_ID**: Get from Create response or Query result\n• **DATA_SOURCE_ID**: Get from \"Get All Data Sources\" request\n• **TAG_ID**: Get from \"Get Tag Values\" request ('id' field)\n• **PROPERTY_ID**: Get from \"Get Property Types\" request ('id' field)\n\n**API CAPABILITIES**\n• **Query Operations**: Joins, filtering, sorting and pagination\n• **Create/Update**: name, type (create only), description, sender, receiver, data source (create only), tags, properties, metadata\n• **Metadata Management**: Additive governance and compliance metadata\n• **Classification**: Structured tags and properties for enterprise taxonomy\n• **Traffic Analysis**: Real-time monitoring and performance metrics\n• **Data Relationships**: Complete traceability and data source mapping\n\n**INTEGRATION TYPE CODES (current release)**\n• **SAP**: 17 SAP_ODATA, 18 SAP_SOAP, 19 SAP_EVENTMESH, 20 SAP_IDOC, 21 SAP_XI, 22 SAP_FILE, 23 SAP_IS_APIM, 24 SAP_IS_CI, 25 SAP_PO, 28 SAP_RFC, 29 SAP_PO_CI, 33 SAP_ASAPIO, 34 SAP_ICF, 35 SAP_COM\n• **Microsoft Azure**: 3 AZURE_APIM, 4 AZURE_EVENTGRID, 5 AZURE_LA_CON, 6 AZURE_LA_STD, 7 AZURE_SB_QUEUE, 8 AZURE_SB_TOPIC, 9 AZURE_FUNCTION, 10 AZURE_DATA_FACTORY\n• **MuleSoft**: 0 MULE_API, 1 MULE_APP\n• **Other**: 2 APIM, 11 BACKEND, 12 BROKER, 13 CONFLUENT_KAFKA, 14 ESB, 15 OTHER, 16 PLANNED, 26 EAM, 27 SOLACE_QUEUE, 30 MFT, 31 B2B, 32 RESOURCE, 36 ETL\n• Codes are release-specific and shift when new types are added - check them after an upgrade\n\n**FEATURES**\n• **Logical Structure**: Discovery → Core Operations → Advanced Examples\n• **Collection-level Authentication**: No per-request token configuration\n• **Complete API Coverage**: Query, create, update, and metadata management\n• **Enterprise Governance**: Comprehensive metadata and classification support\n• **Performance Monitoring**: Traffic analysis and SLA compliance tools\n\n**VERSION HISTORY**\n• **v1.2.0**: 7 new requests (Get Inventory by Data Source, by System, by Tag, by Property Value; Export Inventory with Tags, Properties & Metadata; End-to-End Integrations with Tags & Properties; Impact Analysis - End-to-End Integrations Using an Interface), integration type codes updated to the current release, End-to-End mapping fixed (`seq` instead of the removed `sequence`), case-insensitive name search (`ilike`), update behavior documented (updates replace sender, receiver, tags and objects; type cannot be changed)\n• **v1.1.1**: Fixed integration type documentation (corrected type ID mappings - verified from API)\n• **v1.1.0**: Collection-level authentication, standardized URLs, comprehensive example coverage, enterprise governance features, traffic monitoring capabilities\n• **v1.0.0**: Initial release with basic CRUD operations\n\n**REQUEST OVERVIEW**\n**27 total requests**: 6 Query + 3 Mutations + 18 Examples\n• **19 requests** ready to use immediately\n• **8 requests** require optional variables (clearly marked)",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json",
    "_exporter_id": "15648896"
  },
  "variable": [
    {
      "key": "WHINT_BASE_URL",
      "value": "",
      "description": "Your Integration Cockpit instance domain only (e.g., your-instance.cfapps.eu10.hana.ondemand.com) - without https:// or /api",
      "type": "string"
    },
    {
      "key": "BEARER_TOKEN",
      "value": "",
      "description": "Access token from Settings → Connectivity → Data Sources → API → Tokens",
      "type": "string"
    },
    {
      "key": "DATA_SOURCE_ID",
      "value": "",
      "description": "Optional - Get from \"Get All Data Sources\" request. Used by \"Get Inventory by Data Source\".",
      "type": "string"
    },
    {
      "key": "EXAMPLE_ID",
      "value": "",
      "description": "Optional - Get from Create response or any Query result. Required for Update/Metadata operations.",
      "type": "string"
    },
    {
      "key": "TAG_ID",
      "value": "",
      "description": "Optional - Primary record ID from \"Get Tag Values\" response ('id' field)",
      "type": "string"
    },
    {
      "key": "PROPERTY_ID",
      "value": "",
      "description": "Optional - Primary record ID from \"Get Property Types\" response ('id' field)",
      "type": "string"
    }
  ],
  "auth": {
    "type": "bearer",
    "bearer": [
      {
        "key": "token",
        "value": "{{BEARER_TOKEN}}",
        "type": "string"
      }
    ]
  },
  "item": [
    {
      "name": "1. Query - Core Discovery",
      "item": [
        {
          "name": "01 - Get All Inventory Items",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\"\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "Start here for complete integration landscape overview.\n\nRetrieves all integration inventory with full field structure for understanding data model.\n\n**Use Cases:**\n• Initial discovery and landscape assessment\n• Understanding available fields and data structure\n• Complete integration catalog export\n\n**SQL Equivalent:** `SELECT * FROM inventory`"
          },
          "response": []
        },
        {
          "name": "02 - Get Essential Inventory Fields",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"type\", \"name\", \"sender_name\", \"receiver_name\", \"description\"]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "Optimized query for performance and essential reporting.\n\nRetrieves core integration metadata without excessive data transfer.\n\n**Use Cases:**\n• Dashboard and reporting requirements\n• Integration catalog with performance optimization\n• Business stakeholder communication\n\n**SQL Equivalent:** `SELECT id, type, name, sender_name, receiver_name, description FROM inventory`"
          },
          "response": []
        },
        {
          "name": "03 - Get Integration Types Reference",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"type\", \"name\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\n        \"field\": {\n          \"name\": \"type\",\n          \"eq\": \"23\"\n        }\n      }]\n    }]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "Learn filtering patterns with integration type examples.\n\n**Performance Note:** Use `\"limit\"` parameter for large datasets to prevent instance overload.\n\n**Common Types:**\n• 23: SAP IS API Management (SAP_IS_APIM)\n• 24: SAP Integration Suite Cloud Integration (SAP_IS_CI)\n• 25: SAP Process Orchestration (SAP_PO)\n• 19: SAP Event Mesh (SAP_EVENTMESH)\n\n**Type codes are release-specific:** they shift when new integration types are added (SAP IS API Management was 20 in v1.1.1 and is 23 today). Use the codes listed in the collection description for your release.\n\n**Use Cases:**\n• Technology-specific analysis\n• Platform migration planning\n• Integration type discovery\n\n**SQL Equivalent:** `SELECT type, name FROM inventory WHERE type = 23`"
          },
          "response": []
        },
        {
          "name": "04 - Get Inventory Items with Data Source Join",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\n        \"field\": {\n          \"name\": \"type\",\n          \"eq\": \"23\"\n        }\n      }]\n    }],\n    \"with\": [{\n      \"entity\": \"dataSource\",\n      \"fields\": [\"id\", \"name\"]\n    }]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "JOIN operations linking inventory with data source information.\n\n**Purpose:** Demonstrates relationship patterns and data source traceability.\n\n**Use Cases:**\n• Integration discovery audit trails\n• Data source impact analysis\n• Governance and compliance reporting\n• Understanding which systems discovered specific integrations\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type, ds.id, ds.name FROM inventory i JOIN dataSource ds ON i.data_source_id = ds.id WHERE i.type = 23`\n\n**Copy Data Source IDs from response for advanced filtering examples.**"
          },
          "response": []
        },
        {
          "name": "05 - Get All Data Sources",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"dataSource\"\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "Data source landscape and discovery mechanism overview.\n\nRetrieves all configured data sources for traceability analysis.\n\n**Use Cases:**\n• Data source management and oversight\n• Traceability and governance reporting\n• Discovery mechanism validation\n• Get DATA_SOURCE_ID values for advanced filtering operations\n\n**Response Usage:** Copy 'id' values to {{DATA_SOURCE_ID}} variable for \"Get Inventory by Data Source\". Use the 'id' of your API data source as `data_source_id` in \"01 - Create Inventory Item\"."
          },
          "response": []
        },
        {
          "name": "06 - Get Systems Inventory",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"query\": {\n    \"entity\": \"system\"\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "Complete system landscape documentation.\n\nRetrieves all connected systems in the integration architecture.\n\n**Use Cases:**\n• Architecture documentation and visualization\n• System landscape management\n• Integration endpoint discovery\n• Enterprise architecture alignment\n\n**SQL Equivalent:** `SELECT * FROM system`\n\n**Response Usage:** Copy 'id' values for `sender_id` / `receiver_id` in \"01 - Create Inventory Item\" and \"02 - Update Inventory Item\"."
          },
          "response": []
        }
      ],
      "description": "**Core Discovery:** Essential operations for understanding integration landscape.\n\nAll 6 requests ready to execute immediately after basic variable setup. Begin here for systematic API exploration."
    },
    {
      "name": "2. Mutations - Core Operations",
      "item": [
        {
          "name": "01 - Create Inventory Item",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"upsert\": {\n    \"inventory\": [\n      {\n        \"name\": \"Customer Data Synchronization\",\n        \"description\": \"Bidirectional customer data sync between CRM and ERP systems\",\n        \"type\": 23\n      }\n    ]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "**API Reality:** Creates an inventory item. `name` and `type` are required, `type` cannot be changed later.\n\n**What Works:**\n• name: Integration display name\n• type: Integration platform type (e.g., 23 = SAP IS API Management in the current release)\n• description: Business purpose description\n• sender_id, receiver_id: System IDs from \"06 - Get Systems Inventory\"\n• sender_name, receiver_name: Text only, does not link a system - use sender_id / receiver_id for that\n• data_source_id: ID of your API data source from \"05 - Get All Data Sources\" (recommended: the item then shows in the Cockpit under this data source, so it is clear that it was created via the API)\n• tags, properties, metadata: see \"Advanced Operations\"\n\n**Response:** Returns array with new object ID - save for update operations.\n\n**Use Cases:** Simple integration object creation, basic inventory management"
          },
          "response": []
        },
        {
          "name": "02 - Update Inventory Item",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"upsert\": {\n    \"inventory\": [\n      {\n        \"id\": \"{{EXAMPLE_ID}}\",\n        \"name\": \"Customer Data Synchronization - Enhanced\",\n        \"description\": \"Bidirectional customer data sync with error handling and monitoring\",\n        \"type\": 23\n      }\n    ]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "**Requires {{EXAMPLE_ID}}:** Set from Create response or Query result first.\n\n**Important:** An update replaces the item's sender, receiver, tags and objects with what you send. Send `sender_id`, `receiver_id` and the complete `tags` list along, otherwise they are removed. Query the item first with `\"fields\": [\"id\", \"name\", \"sender_id\", \"receiver_id\"]` and `\"with\": [{\"entity\": \"tags\", \"fields\": [\"id\"]}]` to get the current values.\n\n**Updatable Fields:**\n• name: Modified integration name (required)\n• description: Enhanced business description\n• sender_id, receiver_id: Sender and receiver system\n• tags: Complete list of tags\n\n**Non-Updatable:**\n• type: stays as created, a different value is ignored\n• data_source_id: stays as created\n\n**Use Cases:** Integration lifecycle management, documentation updates"
          },
          "response": []
        },
        {
          "name": "03 - Add Metadata (Additive)",
          "request": {
            "method": "POST",
            "header": [
              {
                "key": "Content-Type",
                "value": "application/json"
              }
            ],
            "body": {
              "mode": "raw",
              "raw": "{\n  \"upsert\": {\n    \"inventory\": [\n      {\n        \"id\": \"{{EXAMPLE_ID}}\",\n        \"name\": \"Customer Data Synchronization - With Metadata\",\n        \"type\": 23,\n        \"metadata\": [\n          {\"name\": \"BUSINESS_OWNER\", \"value\": \"Customer Operations Team\"},\n          {\"name\": \"TECHNICAL_CONTACT\", \"value\": \"integration@company.com\"},\n          {\"name\": \"ENVIRONMENT\", \"value\": \"PRODUCTION\"}\n        ]\n      }\n    ]\n  }\n}",
              "options": {
                "raw": {
                  "language": "json"
                }
              }
            },
            "url": {
              "raw": "https://{{WHINT_BASE_URL}}/api",
              "protocol": "https",
              "host": [
                "{{WHINT_BASE_URL}}"
              ],
              "path": [
                "api"
              ]
            },
            "description": "**Requires {{EXAMPLE_ID}}:** Set from Create response or Query result first.\n\n**Important:** An update replaces the item's sender, receiver, tags and objects with what you send. Send `sender_id`, `receiver_id` and the complete `tags` list along, otherwise they are removed. Query the item first with `\"fields\": [\"id\", \"name\", \"sender_id\", \"receiver_id\"]` and `\"with\": [{\"entity\": \"tags\", \"fields\": [\"id\"]}]` to get the current values.\n\n**Metadata Behavior:**\n• **Additive:** Entries without `id` are added to the existing metadata\n• **Updates:** To change a value, send the entry with its `id` (from a query with `\"with\": [{\"entity\": \"metadata\", \"fields\": [\"id\", \"name\", \"value\"]}]`)\n• **No Individual Deletion:** Single metadata entries cannot be removed via the API\n• **Required Fields:** `name` is required, `type` is ignored on updates\n\n**Use Cases:** Governance tagging, contact information, environment marking, compliance data"
          },
          "response": []
        }
      ],
      "description": "**Core CRUD Operations:** Create, update, and metadata management.\n\nCreate runs right away, Update and Add Metadata require the EXAMPLE_ID variable. Every update replaces sender, receiver, tags and objects - see the request descriptions."
    },
    {
      "name": "3. Examples - Advanced Patterns",
      "item": [
        {
          "name": "Discovery",
          "item": [
            {
              "name": "Get Tag Values",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"tagValue\"\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Discovery Step:** Get all available tag values and their record IDs.\n\n**Purpose:** Tags require existing record ID references - you cannot create custom tags via API.\n\n**Important:** Use the 'id' field from the response, not the 'tag_id' field.\n\n**Usage Pattern:**\n1. Run this query to see available tags\n2. Find your desired tag (e.g., \"decommissioned\")\n3. Copy its 'id' value (e.g., \"IOWcT-he8Fc\")\n4. Set {{TAG_ID}} variable with this value\n5. Use in \"Add Tags to Inventory Item\" or \"Get Inventory by Tag\"\n\n**Response Structure:** Each tag has 'id' (primary key), 'value' (tag name), and 'tag_id' (category reference).\n\n**Enterprise Implication:** Tag taxonomy must be pre-configured in Integration Cockpit UI."
              },
              "response": []
            },
            {
              "name": "Get Property Types",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"propertyType\"\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Discovery Step:** Get all available property types and their record IDs.\n\n**Purpose:** Properties require existing record ID references - you cannot create custom property types via API.\n\n**⚠️ CRITICAL:** Copy the 'id' field from the response!\n\n**Usage Pattern:**\n1. Run this query to see available property types\n2. Find your desired property type (e.g., \"Priority Level\")\n3. Copy its 'id' value (e.g., \"V3G9lX8iEO4\")\n4. Set {{PROPERTY_ID}} variable with this 'id' value\n5. Use in \"Add Properties to Inventory Item\" or \"Get Inventory by Property Value\"\n\n**Response Structure:** Each property type has 'id' (use this), 'name', data type, and validation rules.\n\n**Enterprise Implication:** Property schema must be pre-configured in Integration Cockpit UI."
              },
              "response": []
            }
          ],
          "description": "**Prerequisite Discovery:** Get IDs needed for tags and properties operations."
        },
        {
          "name": "Advanced Operations",
          "item": [
            {
              "name": "Add Tags to Inventory Item",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"upsert\": {\n    \"inventory\": [\n      {\n        \"id\": \"{{EXAMPLE_ID}}\",\n        \"name\": \"Customer Data Synchronization - Tagged\",\n        \"description\": \"Integration with classification tags\",\n        \"tags\": [\n          {\n            \"id\": \"{{TAG_ID}}\"\n          }\n        ]\n      }\n    ]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires Variables:**\n• {{EXAMPLE_ID}}: From Create response or Query result\n• {{TAG_ID}}: Primary record ID from \"Get Tag Values\" response\n\n**Important:** Use the 'id' field value from the tag record, not the 'tag_id' field.\n\n**Step-by-Step Process:**\n1. Run \"Get Tag Values\" to see available tags\n2. Find your desired tag (e.g., value: \"decommissioned\")\n3. Copy its 'id' field value (e.g., \"IOWcT-he8Fc\")\n4. Set {{TAG_ID}} = \"IOWcT-he8Fc\"\n5. Run this request to apply the tag\n\n**Tag Behavior:**\n• Uses existing tag taxonomy only\n• Cannot create new tag values via API\n• The `tags` list replaces all current tags of the item: include every tag it should keep\n• Multiple tags can be applied simultaneously\n\n**Important:** An update replaces the item's sender, receiver, tags and objects with what you send. Send `sender_id`, `receiver_id` and the complete `tags` list along, otherwise they are removed. Query the item first with `\"fields\": [\"id\", \"name\", \"sender_id\", \"receiver_id\"]` and `\"with\": [{\"entity\": \"tags\", \"fields\": [\"id\"]}]` to get the current values.\n\n**Use Cases:** Classification, categorization, filtering enhancement"
              },
              "response": []
            },
            {
              "name": "Add Properties to Inventory Item",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"upsert\": {\n    \"inventory\": [\n      {\n        \"id\": \"{{EXAMPLE_ID}}\",\n        \"name\": \"Customer Data Synchronization - With Properties\",\n        \"description\": \"Integration with typed properties\",\n        \"properties\": [\n          {\n            \"type_id\": \"{{PROPERTY_ID}}\",\n            \"value\": \"CRITICAL_PRIORITY\"\n          }\n        ]\n      }\n    ]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires Variables:**\n• {{EXAMPLE_ID}}: From Create response or Query result\n• {{PROPERTY_ID}}: Primary record ID from \"Get Property Types\" response\n\n**Important:** Use the 'id' field value from the property type record.\n\n**Step-by-Step Process:**\n1. Run \"Get Property Types\" to see available property types\n2. Find your desired property type (e.g., name: \"Priority Level\")\n3. Copy its 'id' field value (e.g., \"V3G9lX8iEO4\")\n4. Set {{PROPERTY_ID}} = \"V3G9lX8iEO4\"\n5. Run this request with your property value\n\n**Property Behavior:**\n• Uses existing property schema only\n• Cannot create new property types via API\n• Each property without `id` is added as a new entry: sending the same property twice creates two entries\n• To change a value, send the property with its `id` and `type_id`\n• Values must conform to property type validation\n\n**Important:** An update replaces the item's sender, receiver, tags and objects with what you send. Send `sender_id`, `receiver_id` and the complete `tags` list along, otherwise they are removed. Query the item first with `\"fields\": [\"id\", \"name\", \"sender_id\", \"receiver_id\"]` and `\"with\": [{\"entity\": \"tags\", \"fields\": [\"id\"]}]` to get the current values.\n\n**Use Cases:** Configuration parameters, business rules, technical specifications"
              },
              "response": []
            }
          ],
          "description": "**Advanced Data Management:** Tags and properties operations requiring ID lookups."
        },
        {
          "name": "Query Patterns",
          "item": [
            {
              "name": "Search Integrations by Name Pattern",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"sender_name\", \"receiver_name\", \"type\"],\n    \"where\": [{\n      \"option\": 1,\n      \"conditions\": [\n        {\n          \"field\": {\n            \"name\": \"name\",\n            \"ilike\": \"Customer\"\n          }\n        }\n      ]\n    }]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Text-based search using ILIKE (case-insensitive) with OR logic.\n\n**Customization:** Change \"Customer\" to any search term.\n\n**Text Operators:**\n• `ilike`: contains text, ignores upper/lower case\n• `like`: contains text, case-sensitive\n\n**Logic Options:**\n• option: 0 = AND logic (all conditions must match)\n• option: 1 = OR logic (any condition can match)\n\n**Use Cases:**\n• Content discovery by business domain\n• Integration name searches\n• Business context filtering\n\n**SQL Equivalent:** `SELECT id, name, sender_name, receiver_name, type FROM inventory WHERE name ILIKE '%Customer%'`"
              },
              "response": []
            },
            {
              "name": "Get Inventory by Data Source",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\"field\": {\"name\": \"data_source_id\", \"eq\": \"{{DATA_SOURCE_ID}}\"}}]\n    }],\n    \"with\": [{\"entity\": \"dataSource\", \"fields\": [\"name\"]}],\n    \"limit\": 1000\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires {{DATA_SOURCE_ID}}:** Get from \"05 - Get All Data Sources\" (use the 'id' field).\n\n**Pattern:** Filter inventory items by the data source that discovered them.\n\n**Customization:** To filter by data source name instead of ID, replace the condition with\n`{\"entity\": {\"name\": \"dataSource\", \"predicates\": [{\"conditions\": [{\"field\": {\"name\": \"name\", \"eq\": \"Your Data Source\"}}]}]}}`\n\n**Use Cases:**\n• Inventory of one tenant or system landscape\n• Checking the result of a data source run\n• Comparing landscapes per environment\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type, ds.name FROM inventory i JOIN dataSource ds ON i.data_source_id = ds.id WHERE i.data_source_id = '{{DATA_SOURCE_ID}}'`"
              },
              "response": []
            },
            {
              "name": "Get Inventory by System (Sender or Receiver)",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\"],\n    \"where\": [{\n      \"option\": 1,\n      \"conditions\": [\n        {\n          \"entity\": {\n            \"name\": \"sender\",\n            \"predicates\": [{\n              \"conditions\": [{\"field\": {\"name\": \"name\", \"eq\": \"SAP S/4HANA\"}}]\n            }]\n          }\n        },\n        {\n          \"entity\": {\n            \"name\": \"receiver\",\n            \"predicates\": [{\n              \"conditions\": [{\"field\": {\"name\": \"name\", \"eq\": \"SAP S/4HANA\"}}]\n            }]\n          }\n        }\n      ]\n    }],\n    \"with\": [\n      {\"entity\": \"sender\", \"fields\": [\"name\"]},\n      {\"entity\": \"receiver\", \"fields\": [\"name\"]}\n    ],\n    \"limit\": 1000\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** OR logic across sender and receiver returns every inventory item connected to the system.\n\n**Customization:** Replace \"SAP S/4HANA\" with your system name.\n\n**Note:** System names can exist once per data source. The name filter returns the inventory items of all of them. For exactly one system, use `{\"field\": {\"name\": \"sender_id\", \"eq\": \"<system id>\"}}` and `{\"field\": {\"name\": \"receiver_id\", \"eq\": \"<system id>\"}}` instead.\n\n**Use Cases:**\n• Impact analysis before a system migration or upgrade\n• System documentation\n• Interface lists for system owners\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type FROM inventory i LEFT JOIN system s ON i.sender_id = s.id LEFT JOIN system r ON i.receiver_id = r.id WHERE s.name = 'SAP S/4HANA' OR r.name = 'SAP S/4HANA'`"
              },
              "response": []
            },
            {
              "name": "Get Inventory by Tag",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\n        \"entity\": {\n          \"name\": \"tags\",\n          \"predicates\": [{\n            \"conditions\": [{\"field\": {\"name\": \"id\", \"in\": {\"value\": [\"{{TAG_ID}}\"]}}}]\n          }]\n        }\n      }]\n    }],\n    \"with\": [{\n      \"entity\": \"tags\",\n      \"fields\": [\"value\", \"tag_id\"],\n      \"with\": [{\"entity\": \"tag\", \"fields\": [\"name\"]}]\n    }],\n    \"limit\": 1000\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires {{TAG_ID}}:** 'id' from \"Get Tag Values\" (not 'tag_id').\n\n**Pattern:** The `where` condition on `tags` selects the inventory items, `with` returns their tags.\n\n**Customization:**\n• Without this tag: add `\"not\": true` next to `\"entity\"` in the condition\n• Any of several tags: add more IDs to the `value` list\n\n**Use Cases:**\n• Decommissioning and migration lists\n• Classification reports\n• Governance reviews\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type FROM inventory i JOIN tagValue t ON t.inventory_id = i.id WHERE t.id IN ('{{TAG_ID}}')`"
              },
              "response": []
            },
            {
              "name": "Get Inventory by Property Value",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\n        \"entity\": {\n          \"name\": \"properties\",\n          \"predicates\": [{\n            \"conditions\": [\n              {\"field\": {\"name\": \"type_id\", \"eq\": \"{{PROPERTY_ID}}\"}},\n              {\"field\": {\"name\": \"value\", \"eq\": \"Yes\"}}\n            ]\n          }]\n        }\n      }]\n    }],\n    \"with\": [{\n      \"entity\": \"properties\",\n      \"fields\": [\"type_id\", \"value\"],\n      \"with\": [{\"entity\": \"type\", \"fields\": [\"name\"]}]\n    }],\n    \"limit\": 1000\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires {{PROPERTY_ID}}:** 'id' from \"Get Property Types\".\n\n**Pattern:** Both conditions sit in the same `properties` predicate, so property type and value must match on the same property.\n\n**Customization:** Replace \"Yes\" with the value you are looking for. For value-list properties, use the text of the list entry. If the list entry was renamed later, filter on the list entry instead: replace the `value` condition with `{\"entity\": {\"name\": \"valueList\", \"predicates\": [{\"conditions\": [{\"field\": {\"name\": \"name\", \"eq\": \"Yes\"}}]}]}}`.\n\n**Use Cases:**\n• Inventory items per team, owner or business domain\n• Lists for audits and reviews\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type FROM inventory i JOIN properties p ON p.inventory_id = i.id WHERE p.type_id = '{{PROPERTY_ID}}' AND p.value = 'Yes'`"
              },
              "response": []
            },
            {
              "name": "Get Multiple Integration Types",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\", \"description\"],\n    \"where\": [{\n      \"option\": 1,\n      \"conditions\": [\n        {\"field\": {\"name\": \"type\", \"eq\": \"23\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"24\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"25\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"19\"}}\n      ]\n    }]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Multi-type filtering for platform family analysis.\n\n**Types Included:**\n• 23: SAP IS API Management (SAP_IS_APIM)\n• 24: SAP Integration Suite Cloud Integration (SAP_IS_CI)\n• 25: SAP Process Orchestration (SAP_PO)\n• 19: SAP Event Mesh (SAP_EVENTMESH)\n\n**Type codes are release-specific:** they shift when new integration types are added (SAP IS API Management was 20 in v1.1.1 and is 23 today). Use the codes listed in the collection description for your release.\n\n**Customization:** Add/remove type conditions as needed.\n\n**Use Cases:**\n• Platform family analysis (all SAP integrations)\n• Migration planning (PO to IS CI)\n• Technology consolidation assessment\n\n**SQL Equivalent:** `SELECT id, name, type, description FROM inventory WHERE type IN (23, 24, 25, 19)`"
              },
              "response": []
            },
            {
              "name": "Get Complete SAP Integration Landscape",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\", \"sender_name\", \"receiver_name\"],\n    \"where\": [{\n      \"option\": 1,\n      \"conditions\": [\n        {\"field\": {\"name\": \"type\", \"eq\": \"16\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"17\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"18\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"19\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"20\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"21\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"22\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"23\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"24\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"25\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"26\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"27\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"28\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"29\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"33\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"34\"}},\n        {\"field\": {\"name\": \"type\", \"eq\": \"35\"}}\n      ]\n    }]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Complete SAP ecosystem export with all platform types.\n\n**SAP Types Included:**\n• 16: Planned Integration (PLANNED)\n• 17: SAP OData Services (SAP_ODATA)\n• 18: SAP SOAP Services (SAP_SOAP)\n• 19: SAP Event Mesh (SAP_EVENTMESH)\n• 20: SAP IDoc Interfaces (SAP_IDOC)\n• 21: SAP XI Messages (SAP_XI)\n• 22: SAP File Interfaces (SAP_FILE)\n• 23: SAP IS API Management (SAP_IS_APIM)\n• 24: SAP Integration Suite Cloud Integration (SAP_IS_CI)\n• 25: SAP Process Orchestration (SAP_PO)\n• 26: Enterprise Architecture Management (EAM)\n• 27: Solace Queues (SOLACE_QUEUE)\n• 28: SAP RFC Interfaces (SAP_RFC)\n• 29: SAP PO CI (SAP_PO_CI)\n• 33: SAP ASAPIO (SAP_ASAPIO)\n• 34: SAP ICF Services (SAP_ICF)\n• 35: SAP Communication Arrangements (SAP_COM)\n\n**Type codes are release-specific:** they shift when new integration types are added (SAP IS API Management was 20 in v1.1.1 and is 23 today). Use the codes listed in the collection description for your release.\n\n**Use Cases:**\n• Complete SAP integration inventory\n• Enterprise architecture documentation\n• SAP platform consolidation analysis\n• Migration and modernization planning\n\n**SQL Equivalent:** `SELECT id, name, type, sender_name, receiver_name FROM inventory WHERE type IN (16,17,18,19,20,21,22,23,24,25,26,27,28,29,33,34,35)`"
              },
              "response": []
            },
            {
              "name": "Get Inventory with Metadata Context",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\", \"description\"],\n    \"with\": [\n      {\n        \"entity\": \"metadata\",\n        \"fields\": [\"name\", \"value\"]\n      }\n    ]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** JOIN operations for enriched data retrieval.\n\n**Relationships:** Links inventory items with their metadata for complete governance context.\n\n**Use Cases:**\n• Governance reporting with metadata context\n• Compliance auditing with ownership information\n• Complete integration documentation\n• Business process mapping with extended attributes\n\n**SQL Equivalent:** `SELECT i.id, i.name, i.type, i.description, m.name, m.value FROM inventory i LEFT JOIN metadata m ON i.id = m.inventory_id`"
              },
              "response": []
            },
            {
              "name": "Export Inventory with Tags, Properties & Metadata",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"inventory\",\n    \"fields\": [\"id\", \"name\", \"type\", \"description\"],\n    \"with\": [\n      {\"entity\": \"sender\", \"fields\": [\"name\"]},\n      {\"entity\": \"receiver\", \"fields\": [\"name\"]},\n      {\n        \"entity\": \"tags\",\n        \"fields\": [\"value\", \"tag_id\"],\n        \"with\": [{\"entity\": \"tag\", \"fields\": [\"name\"]}]\n      },\n      {\n        \"entity\": \"properties\",\n        \"fields\": [\"type_id\", \"value\"],\n        \"with\": [{\"entity\": \"type\", \"fields\": [\"name\"]}]\n      },\n      {\"entity\": \"metadata\", \"fields\": [\"name\", \"value\"]}\n    ],\n    \"order\": [{\"field\": \"id\"}],\n    \"limit\": 1000,\n    \"offset\": 0\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Complete inventory export with sender, receiver, tags, properties and metadata.\n\n**Pagination:** `order` by `id` keeps the row order identical between pages. Increase `offset` by 1000 until fewer than 1000 rows are returned.\n\n**Use Cases:**\n• Complete inventory backup\n• Environment migration\n• Governance and compliance reporting\n\n**SQL Equivalent:** Multi-table JOIN of inventory with systems, tags, properties and metadata."
              },
              "response": []
            },
            {
              "name": "Monitor BTP Integration Performance",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"btpCloudIntegrationMessage\",\n    \"fields\": [\"sender\", \"artefact\", \"package\", \"duration\", \"status\", \"started_on\"],\n    \"where\": [{\n      \"conditions\": [{\n        \"field\": {\n          \"name\": \"started_on\",\n          \"gt_time\": \"2025-09-01T00:00:00.000Z\"\n        }\n      }]\n    }],\n    \"limit\": 200\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Time-based traffic monitoring with performance metrics.\n\n**Time Filtering:** Messages processed since September 1, 2025 (adjust as needed).\n\n**Customization:**\n• Change date in \"gt_time\" for different time periods\n• Adjust limit for more/fewer results\n• Add status filtering for error analysis\n\n**Use Cases:**\n• SLA compliance monitoring\n• Performance bottleneck identification\n• Integration health assessment\n• Operational dashboards\n\n**SQL Equivalent:** `SELECT sender, artefact, package, duration, status, started_on FROM btpCloudIntegrationMessage WHERE started_on > '2025-09-01T00:00:00.000Z' LIMIT 200`"
              },
              "response": []
            },
            {
              "name": "Monitor BTP Integration Performance - Time Window",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"btpCloudIntegrationMessage\",\n    \"fields\": [\"sender\", \"artefact\", \"package\", \"duration\", \"status\", \"started_on\"],\n    \"where\": [\n      {\n        \"conditions\": [\n          {\n            \"field\": {\n              \"name\": \"started_on\",\n              \"gt_time\": \"2025-08-31T23:59:59.999Z\"\n            }\n          },\n          {\n            \"field\": {\n              \"name\": \"started_on\",\n              \"lt_time\": \"2025-09-01T00:01:00.001Z\"\n            }\n          }\n        ]\n      }\n    ],\n    \"limit\": 200\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Precise time window filtering using both start and end time boundaries.\n\n**Time Range:** Messages processed between August 31, 2025 23:59:59 and September 1, 2025 00:01:00.\n\n**Advanced Time Filtering:**\n• **gt_time**: Greater than (after) specified timestamp\n• **lt_time**: Less than (before) specified timestamp\n• Combined conditions create precise time windows\n\n**Use Cases:**\n• Incident analysis for specific time periods\n• Batch processing verification\n• Detailed troubleshooting during maintenance windows\n• Compliance reporting for exact time ranges\n\n**Customization:** Adjust both gt_time and lt_time values for your specific analysis period.\n\n**SQL Equivalent:** `SELECT sender, artefact, package, duration, status, started_on FROM btpCloudIntegrationMessage WHERE started_on > '2025-08-31T23:59:59.999Z' AND started_on < '2025-09-01T00:01:00.001Z' LIMIT 200`"
              },
              "response": []
            },
            {
              "name": "End-to-End Integration Flow Mapping",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"dataFlow\",\n    \"with\": [\n      {\n        \"entity\": \"sender\",\n        \"fields\": [\"name\"],\n        \"with\": [\n          {\n            \"entity\": \"dataSource\",\n            \"fields\": [\"name\"]\n          }\n        ]\n      },\n      {\n        \"entity\": \"receiver\",\n        \"fields\": [\"name\"],\n        \"with\": [\n          {\n            \"entity\": \"dataSource\",\n            \"fields\": [\"name\"]\n          }\n        ]\n      },\n      {\n        \"entity\": \"items\",\n        \"fields\": [\"seq\"],\n        \"with\": [\n          {\n            \"entity\": \"inventory\",\n            \"fields\": [\"name\", \"type\"],\n            \"with\": [\n              {\n                \"entity\": \"dataSource\",\n                \"fields\": [\"name\"]\n              }\n            ]\n          }\n        ]\n      }\n    ],\n    \"order\": [{\"field\": \"id\"}],\n    \"limit\": 100\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** Complex multi-level JOINs for complete process flow visualization.\n\n**Relationships Mapped:**\n• dataFlow → sender/receiver systems\n• dataFlow → integration items (`seq` = position of the interface in the End-to-End integration)\n• All entities → data source traceability\n\n**Use Cases:**\n• End-to-end process documentation\n• Integration architecture visualization\n• Business process impact analysis\n• Data lineage and traceability\n\n**SQL Equivalent:** Complex multi-table JOIN with nested relationships for complete flow context.\n\n**Pagination:** Increase `offset` by 100 until fewer than 100 rows are returned. `order` keeps the row order identical between pages."
              },
              "response": []
            },
            {
              "name": "End-to-End Integrations with Tags & Properties",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"dataFlow\",\n    \"fields\": [\"id\", \"name\", \"description\"],\n    \"with\": [\n      {\n        \"entity\": \"tags\",\n        \"fields\": [\"value\", \"tag_id\"],\n        \"with\": [{\"entity\": \"tag\", \"fields\": [\"name\"]}]\n      },\n      {\n        \"entity\": \"properties\",\n        \"fields\": [\"type_id\", \"value\", \"value_list_id\"],\n        \"with\": [\n          {\"entity\": \"type\", \"fields\": [\"name\"]},\n          {\"entity\": \"valueList\", \"fields\": [\"name\"]}\n        ]\n      }\n    ],\n    \"order\": [{\"field\": \"id\"}],\n    \"limit\": 100,\n    \"offset\": 0\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Pattern:** End-to-End integrations with their tags and properties.\n\n**Filter vs. Join:** A `where` condition on `tags` or `properties` only decides which End-to-End integrations are returned. Tags and properties appear in the response only when you add them to `with`.\n\n**Response:**\n• `tags`: tag value plus the tag name (`tag.name`)\n• `properties`: property value plus the property type (`type.name`)\n• Value-list properties also return the list entry (`value_list.name`). `value` keeps the text that was selected; if the list entry is renamed later, only `value_list.name` shows the new name.\n\n**Customization:**\n• Only one property type: add a `where` inside the `properties` block, e.g. `\"where\": [{\"conditions\": [{\"field\": {\"name\": \"type_id\", \"eq\": \"{{PROPERTY_ID}}\"}}]}]`.\n• Filter by tag or property: combine with a `where` on the End-to-End integration, e.g. `{\"entity\": {\"name\": \"tags\", \"predicates\": [{\"conditions\": [{\"field\": {\"name\": \"id\", \"in\": {\"value\": [\"{{TAG_ID}}\"]}}}]}]}}` (add `\"not\": true` to exclude).\n\n**Pagination:** Increase `offset` by 100 until fewer than 100 rows are returned. `order` keeps the row order identical between pages.\n\n**Use Cases:**\n• Export of End-to-End integrations with their classification\n• Governance reporting\n• Impact analysis by tag or property\n\n**SQL Equivalent:** `SELECT f.id, f.name, t.value, p.value FROM dataFlow f LEFT JOIN tagValue t ON t.data_flow_id = f.id LEFT JOIN properties p ON p.data_flow_id = f.id`"
              },
              "response": []
            },
            {
              "name": "Impact Analysis - End-to-End Integrations Using an Interface",
              "request": {
                "method": "POST",
                "header": [
                  {
                    "key": "Content-Type",
                    "value": "application/json"
                  }
                ],
                "body": {
                  "mode": "raw",
                  "raw": "{\n  \"query\": {\n    \"entity\": \"dataFlow\",\n    \"fields\": [\"id\", \"name\"],\n    \"where\": [{\n      \"option\": 0,\n      \"conditions\": [{\n        \"entity\": {\n          \"name\": \"items\",\n          \"predicates\": [{\n            \"conditions\": [{\"field\": {\"name\": \"inventory_id\", \"eq\": \"{{EXAMPLE_ID}}\"}}]\n          }]\n        }\n      }]\n    }],\n    \"with\": [{\n      \"entity\": \"items\",\n      \"fields\": [\"seq\", \"inventory_id\"],\n      \"with\": [{\"entity\": \"inventory\", \"fields\": [\"name\", \"type\"]}]\n    }]\n  }\n}",
                  "options": {
                    "raw": {
                      "language": "json"
                    }
                  }
                },
                "url": {
                  "raw": "https://{{WHINT_BASE_URL}}/api",
                  "protocol": "https",
                  "host": [
                    "{{WHINT_BASE_URL}}"
                  ],
                  "path": [
                    "api"
                  ]
                },
                "description": "**Requires {{EXAMPLE_ID}}:** ID of an inventory item (from any inventory query).\n\n**Pattern:** Returns every End-to-End integration that contains the inventory item, with the complete chain of interfaces (`seq` = position in the chain).\n\n**Use Cases:**\n• Change impact before modifying or decommissioning an interface\n• Business process impact analysis\n• Incident analysis\n\n**SQL Equivalent:** `SELECT f.id, f.name FROM dataFlow f JOIN items i ON i.data_flow_id = f.id WHERE i.inventory_id = '{{EXAMPLE_ID}}'`"
              },
              "response": []
            }
          ],
          "description": "**Advanced Query Patterns:** Complex filtering, joins, and monitoring operations for enterprise integration management.\n\n• **Filter:** name, integration type, data source, system, tag, property value\n• **Export:** inventory items and End-to-End integrations with tags, properties and metadata\n• **Monitor:** BTP Cloud Integration message traffic\n• **End-to-End:** flow mapping and impact analysis"
        }
      ],
      "description": "**Advanced Patterns:** Discovery, classification and query examples for enterprise integration management.\n\nDiscovery gets the tag and property IDs, Advanced Operations assigns tags and properties, Query Patterns covers filtering, exports, traffic monitoring and End-to-End integrations. Requests that need an optional variable say so at the top of their description (\"Requires\")."
    }
  ]
}