How to grab data from the body and from the response of the call and use this data in the next call
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
-
Hello @okviga,
You don't seem to be using a Refintiv product/API. For this generic programming question, I would recommend that you ask at stackoverflow.com.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛