Have you had a chance to Review

API Reference Tree

?

if you expand Extractions -> OnDemandExtractions-> ExtractRaw,

The drop-down list for ExtractionRequest will contain all the possible values of ExtractionRequest.

Once you select the preferred ExtractionRequest type from the drop-down list, the reference will reflect all the available and required fields for this specific request type.

Is this reference information what you are looking for?

@akio.tajima

I understand that ReportTemplateTypes and ExtractionRequest are defined for different extraction request type. The ReportTemplateTypes is used for Schedule Extraction, while the ExtractionRequest is used for On-Demand Extraction. As both extraction types should provide similar data, ReportTemplateTypes and ExtractionRequest might be linked, but they should not be converted directly.

If you want to get ContentFieldNames by ExtractionRequest, you can use the GetValidContentFieldTypesForClass endpoint instead.

Hope this helps.

Below is the example.

Request:
GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/GetValidContentFieldTypesForClass(ReportTemplateOrExtractRequestClassName='SingleHistoricalPriceExtractionRequest')

Response:
{
    "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ContentFieldTypes",
    "value": [
        {
            "Code": "TPX.7 Day Compound Yield",
            "Name": "7 Day Compound Yield",
            "Description": "Instrument's calculated 7-day yield that assumes coupon payments are invested at the current market interest rate at the time of receipt and held until maturity",
            "FormatType": "Number",
            "FieldGroup": " "
        },
        {
            "Code": "TPX.7 Day Yield",
            "Name": "7 Day Yield",
            "Description": "Instrument's calculated 7-day yield, including the day on which the figure is reported, as supplied by NASDAQ",
            "FormatType": "Number",
            "FieldGroup": " "
        },

Hello again @akio.tajima,

Thanks for the clarification, now we understand your question better, and I think the answer is that there is no guaranteed direct correspondence between on-demand and template-scheduled requests. Template-based request was designed to mimic GUI-driven request functionality. On-demand was designed separately, and the intention was quick API-based requesting and testing.

Often, there is the same request for on demand and template-based way of extraction, but not always.

Agree with @veerapath.rungruengrayubkul, for your use case GetValidContentFieldTypesForClass request appears to be the best way to find out the available fields for a request type.