How to grab data from the body and from the response of the call and use this data in the next ca...
...ll for the bulk run
Hi Guys,
I have got an interesting task and am not sure how to proceed with this. Maybe you could recommend to me the ways.
POST | URL: ........./release
I have 1 POST request to create the Release for each Project. The request body has the "ProjectID" on it and in the Response body I have got the "ReleaseID"
POST | URL: ............/cycle
The 2nd POST request is to add the "Cycle" to the created release by using the individual "ReleaseIDs" we received in the response body of the previous call and also we need to use the "ProjectID" from the previous request body
Here are the requests to make it more clear:
1st call Body: ____WE NEED to grab "ProjectID" from here
"release": {
"name": "TEST API Releas35",
"description": "",
"startDate": "",
"targetDate": "",
"projectID": "5149"
}
Response: _____WE NEED to grab "releaseID" from here
{
"success": true,
"code": "AD.RELEASE_SUCCESSFUL",
"message": "Release added successfully.",
"data": [
{
"ENTITY_KEY": "{RELEASE$}(TEST API Releas35)",
"releaseID": 39168,
"releaseName": "TEST API Releas35",
"builds": [
{
"name": "LKGB",
"isArchive": false,
"buildID": 70785
}
]
}
]
}
2nd call_to add the cycle to this release:
{
"cycle": {
"name": "{{cycle2}}",
"startDate": "",
"targetDate": "",
"projectID": "{{QMprojectID}}",
"releaseID": "{{versionID}}"
}
}
P.s. We would do that by running the CVC file that has over 50 "ProjectIDs"
Actually, we would send the following requests:
1st:
{
"release": {
"name": "{{version}}",
"description": "{{description}}",
"startDate": "{{Qmstartdate}}",
"targetDate": "{{Qmtargetdate}}",
"projectID": "{{QMprojectID}}"
}
2nd:
{
"cycle": {
"name": "{{cycle2}}",
"startDate": "",
"targetDate": "",
"projectID": "{{QMprojectID}}",
"releaseID": "{{releaseID}}"
}
}
Example of the excel file we use:
Best Answer
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛