Humanitarian Data Exchange

Humanitarian Data Exchange MCP Server

HDX MCP Server provides access to humanitarian data through the Humanitarian Data Exchange (HDX) API - https://data.humdata.org/hapi⁠. This server offers 33 specialized tools for retrieving humanitarian information including affected populations (refugees, IDPs, returnees), baseline demographics, food security indicators, conflict data, funding information, and operational presence across hundreds of countries and territories. See repository for instructions on getting a free HDX_APP_INDENTIFIER for access.

What is an MCP Server?⁠

MCP Info

Image Building Info

Attribute	Details
Dockerfile	https://github.com/dividor/hdx-mcp/blob/c625bf9ae120ed93a36aa7ac9352bdc41f6d9546/Dockerfile⁠
Commit	c625bf9ae120ed93a36aa7ac9352bdc41f6d9546
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/hdx --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence	MIT License

Available Tools (29)

Tools Details

Tool: affected_people_humanitarian_needs_get

OCHA's Humanitarian Needs data, based on the Joint and Intersectoral Analysis Framework (JIAF), provides information about the number of people in need during a crisis. See the more detailed technical HDX HAPI documentation⁠, and the original JIAF source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• category: A category combining gender, age range, disability marker and population group information

• sector_code: Filter the response by the sector code.

• population_status: Filter the response by the population status, available values are described here.⁠

• population_min: Filter the response by a lower bound for the population.

• population_max: Filter the response by a upper bound for the population.

• sector_name: Filter the response by the sector name.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "reference_period_end": "unknown_type",
      "population_status": "AFF",
      "admin2_name": "unknown_type",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "sector_code": "string",
      "population": 1,
      "reference_period_start": "2024-01-01T12:00:00Z",
      "sector_name": "unknown_type",
      "category": "string",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: affected_people_idps_get

Get idps data

🎯 CRITICAL - Data Coverage Warning: Data coverage is only determined by the metadata_data_availability_get tool. Just because a country is in the system doesn't mean it has data. ALWAYS verify data availability before making data queries.

🎯 CRITICAL - Administrative Level Efficiency: Before making aggregate queries (totals, country-wide statistics), ALWAYS check data availability using metadata_data_availability_get for the target country. Use the LOWEST available admin level (0=country, 1=state, 2=district) to avoid downloading excessive granular data. For country totals, use admin level 0 if available, otherwise level 1. Never query admin level 2 for simple aggregations when level 0/1 is sufficient.

🔄 Pagination: You can page through results using limit and offset parameters (limit=records per page, offset=starting position).

⚠️ CRITICAL - Never Manually Aggregate Data: IMPORTANT: Never sum data yourself, only take the data verbatim from the tool. NEVER aggregate totals yourself to answer a question if you do not have the values already aggregated from the tool. Do NOT sum up individual records, calculate country-wide statistics from subnational data, or aggregate across time periods/demographics yourself. If data is not pre-aggregated, inform the user that aggregate data is not available. Always use the most appropriate administrative level that has pre-aggregated data.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "reference_period_end": "unknown_type",
      "assessment_type": "BA",
      "admin2_name": "unknown_type",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "population": 1,
      "operation": "string",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "reporting_round": 1,
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: affected_people_refugees_get

UNHCR's Refugee data provides information about displaced people in a crisis. See the more detailed technical HDX HAPI documentation⁠, and the original HDX source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• population_group: Filter the response by the population group, available values are described here.⁠

• population_min: Filter the response by a lower bound for the population.

• population_max: Filter the response by a upper bound for the population.

• gender: Filter the response by the gender, available values are described here.⁠

• age_range: Filter the response by the age range. These are expressed as [start age]-[end age], or [start age]+ for an age range starting at [start age] or above. The end age is assumed to be inclusive, though that is not always explicit in the source data.

• origin_location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• origin_location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• origin_has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• origin_in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• asylum_location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• asylum_location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• asylum_has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• asylum_in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "resource_hdx_id": "string",
      "population_group": "REF",
      "gender": "f",
      "age_range": "string",
      "min_age": "unknown_type",
      "reference_period_end": "unknown_type",
      "origin_location_code": "string",
      "origin_location_name": "string",
      "population": 1,
      "max_age": "unknown_type",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "asylum_location_code": "string",
      "asylum_location_name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: affected_people_returnees_get

Get returnees data

🎯 CRITICAL - Data Coverage Warning: Data coverage is only determined by the metadata_data_availability_get tool. Just because a country is in the system doesn't mean it has data. ALWAYS verify data availability before making data queries.

🎯 CRITICAL - Administrative Level Efficiency: Before making aggregate queries (totals, country-wide statistics), ALWAYS check data availability using metadata_data_availability_get for the target country. Use the LOWEST available admin level (0=country, 1=state, 2=district) to avoid downloading excessive granular data. For country totals, use admin level 0 if available, otherwise level 1. Never query admin level 2 for simple aggregations when level 0/1 is sufficient.

🔄 Pagination: You can page through results using limit and offset parameters (limit=records per page, offset=starting position).

⚠️ CRITICAL - Never Manually Aggregate Data: IMPORTANT: Never sum data yourself, only take the data verbatim from the tool. NEVER aggregate totals yourself to answer a question if you do not have the values already aggregated from the tool. Do NOT sum up individual records, calculate country-wide statistics from subnational data, or aggregate across time periods/demographics yourself. If data is not pre-aggregated, inform the user that aggregate data is not available. Always use the most appropriate administrative level that has pre-aggregated data.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• population_group: Filter the response by the population group, available values are described here.⁠

• gender: Filter the response by the gender, available values are described here.⁠

• age_range: Filter the response by the age range. These are expressed as [start age]-[end age], or [start age]+ for an age range starting at [start age] or above. The end age is assumed to be inclusive, though that is not always explicit in the source data.

• min_age: The minimum age from age_range, set to null if age_range is "all" and there is no age disaggregation

• max_age: The maximum age from age_range, set to null if age_range is "all" and there is no age disaggregation, or if there is no upper limit to the age range

• origin_location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• origin_location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• origin_has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• origin_in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• asylum_location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• asylum_location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• asylum_has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• asylum_in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "resource_hdx_id": "string",
      "population_group": "REF",
      "gender": "f",
      "age_range": "string",
      "min_age": "unknown_type",
      "reference_period_end": "unknown_type",
      "origin_location_code": "string",
      "origin_location_name": "string",
      "population": 1,
      "max_age": "unknown_type",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "asylum_location_code": "string",
      "asylum_location_name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: baseline_population_get

Baseline population data sourced and maintained by UNFPA (UN Population Fund). See the more detailed technical HDX HAPI documentation⁠, and the UNFPA on HDX⁠.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• gender: Filter the response by the gender, available values are described here.⁠

• age_range: Filter the response by the age range. These are expressed as [start age]-[end age], or [start age]+ for an age range starting at [start age] or above. The end age is assumed to be inclusive, though that is not always explicit in the source data.

• population_min: Filter the response by a lower bound for the population.

• population_max: Filter the response by a upper bound for the population.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "gender": "f",
      "age_range": "string",
      "min_age": "unknown_type",
      "reference_period_end": "unknown_type",
      "admin2_name": "unknown_type",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "population": 1,
      "max_age": "unknown_type",
      "reference_period_start": "unknown_type",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: climate_rainfall_get

Rainfall data . See the more detailed technical <a href="https://hdx-hapi.readthedocs.io/en/latest/data_usage_guides/⁠

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• aggregation_period: Filter the response by the aggregation period, available values are described here.⁠

• version: Version rainfall

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "provider_admin1_code": "unknown_type",
      "version": "unknown_type",
      "reference_period_end": "unknown_type",
      "rainfall": 1.5,
      "provider_admin2_code": "unknown_type",
      "aggregation_period": "dekad",
      "admin2_name": "unknown_type",
      "rainfall_long_term_average": 1.5,
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "rainfall_anomaly_pct": 1.5,
      "number_pixels": "unknown_type",
      "reference_period_start": "unknown_type",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: coordination_conflict_events_get

Armed Conflict Location & Events Data from ACLED. See the more detailed technical HDX HAPI documentation⁠, and the original ACLED source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• event_type: Filter the response by the ACLED event-type categories (non-mutually exclusive), available values are described here.⁠

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "events": "unknown_type",
      "admin_level": 1,
      "event_type": "civilian_targeting",
      "reference_period_end": "unknown_type",
      "admin2_name": "unknown_type",
      "fatalities": "unknown_type",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: coordination_funding_get

OCHA's funding data from the Financial Tracking Service provides information on humanitarian aid contributions. See the more detailed technical HDX HAPI documentation⁠, and the original FTS source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• appeal_code: Filter the response by a unique code given by FTS to each appeal

• appeal_type: Filter the response by the type of the appeal, such as flash or HRP

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "resource_hdx_id": "string",
      "appeal_code": "string",
      "appeal_name": "string",
      "reference_period_end": "unknown_type",
      "funding_pct": "unknown_type",
      "appeal_type": "unknown_type",
      "location_code": "string",
      "requirements_usd": "unknown_type",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "funding_usd": 1.5,
      "location_name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: coordination_national_risk_get

European Commission national risk data from the INFORM-risk framework. See the more detailed technical HDX HAPI documentation⁠, and the original INFORM-risk source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• risk_class: Filter the response by the INFORM risk class, available values are described here.⁠

• global_rank_min: Filter the response by a lower bound for the Global Rank.

• global_rank_max: Filter the response by an upper bound for the Global Rank.

• overall_risk_min: Filter the response by a lower bound for the Overall Risk.

• overall_risk_max: Filter the response by an upper bound for the Overall Risk.

• hazard_exposure_risk_min: Filter the response by a lower bound for the Hazard Exposure Risk.

• hazard_exposure_risk_max: Filter the response by an upper bound for the Hazard Exposure Risk.

• vulnerability_risk_min: Filter the response by a lower bound for the Vulnerability Risk.

• vulnerability_risk_max: Filter the response by an upper bound for the Vulnerability Risk.

• coping_capacity_risk_min: Filter the response by a lower bound for the Coping Capacity Risk.

• coping_capacity_risk_max: Filter the response by a lower bound for the Coping Capacity Risk.

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "risk_class": "1",
      "global_rank": 1,
      "overall_risk": 1.5,
      "location_name": "string",
      "meta_missing_indicators_pct": "unknown_type",
      "reference_period_end": "unknown_type",
      "vulnerability_risk": 1.5,
      "resource_hdx_id": "string",
      "coping_capacity_risk": 1.5,
      "hazard_exposure_risk": 1.5,
      "reference_period_start": "unknown_type",
      "meta_avg_recentness_years": "unknown_type",
      "location_code": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: coordination_operational_presence_get

OCHA's 3W (Who is doing What Where) Operational Presence data provides information about which organizations are working in different locations affected by a crisis. See the more detailed technical HDX HAPI documentation⁠, and the original OCHA 3W source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• sector_code: Filter the response by sector codes, which describe the humanitarian sector to which the operational presence applies. Use the metadata_sector_get tool to get available sector codes and names.

• sector_name: Filter the response by sector names, which describe the humanitarian sector to which the operational presence applies. Use the metadata_sector_get tool to get available sector codes and names.

• org_acronym: Filter the response by the acronym of the organization to which the operational presence applies. Use the metadata_org_get tool to get available organization codes and names.

• org_name: Filter the response by the name of the organization to which the operational presence applies. Use the metadata_org_get tool to get available organization codes and names.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "reference_period_end": "unknown_type",
      "org_type_description": "unknown_type",
      "admin2_name": "unknown_type",
      "org_type_code": "unknown_type",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "sector_code": "string",
      "sector_name": "string",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "org_acronym": "string",
      "org_name": "string",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: food_prices_get

The World Food Programme (WFP) food prices data provides information about food prices for a range of commodities at markets across the world. See the more detailed technical HDX HAPI documentation⁠, and the original WFP source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• market_code: Filter the response by the unique code identifying the market

• market_name: Filter the response by the name of the market

• commodity_code: Filter the response by the unique code identifying the commodity

• commodity_category: Filter the response by the food group that the commodity belongs to, available values are described here.⁠

• commodity_name: Filter the response by the name of the commodity

• price_flag: Filter the response by the pre-processing characteristics of food prices, available values are described here.⁠

• price_type: Filter the response by the point in the supply chain at which the price is determined, available values are described here.⁠

• price_min: Filter the response by a lower bound for the price.

• price_max: Filter the response by a upper bound for the price.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "commodity_code": "string",
      "currency_code": "string",
      "price": 1.5,
      "commodity_category": "cereals and tubers",
      "admin2_code": "unknown_type",
      "admin_level": 1,
      "unit": "string",
      "admin1_name": "unknown_type",
      "commodity_name": "string",
      "lon": "unknown_type",
      "admin2_name": "unknown_type",
      "lat": "unknown_type",
      "market_code": "string",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "reference_period_end": "unknown_type",
      "price_type": "Farm Gate",
      "price_flag": "actual",
      "market_name": "string",
      "resource_hdx_id": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: food_security_get

Integrated Food Security Phase Classification from the IPC. See the more detailed technical HDX HAPI documentation⁠, and the original IPC source⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• ipc_phase: Filter the response by the IPC phase, available values are described here.⁠

• ipc_type: Filter the response by the IPC type, available values are described here.⁠

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "reference_period_end": "unknown_type",
      "ipc_type": "string",
      "admin2_name": "unknown_type",
      "ipc_phase": "string",
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "population_in_phase": 1,
      "reference_period_start": "unknown_type",
      "population_fraction_in_phase": 1.5,
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: hdx_get_dataset_info

Get detailed information about a specific HDX dataset.

Tool: hdx_search_locations

Search for locations (countries) in the HDX system.

Tool: hdx_server_info

Get information about the HDX MCP server instance.

Tool: metadata_admin1_get

Not all data are available for all locations. Learn more about the scope of data coverage in HDX HAPI in the Overview and Getting Started⁠ documentation.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• id: Filter the response by a location (typically a country), using the unique identifier (id) from the location table associated with each entry.

• location_ref: Filter the response by a location (typically a country) reference number.

• code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠.

• name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source.

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "id": 1,
      "location_ref": 1,
      "code": "string",
      "name": "string",
      "from_cods": true,
      "reference_period_start": "2024-01-01T12:00:00Z",
      "reference_period_end": "unknown_type",
      "location_code": "string",
      "location_name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_admin2_get

Not all data are available for all locations. Learn more about the scope of data coverage in HDX HAPI in the Overview and Getting Started⁠ documentation.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• id: Filter the response by a location (typically a country), using the unique identifier (id) from the location table associated with each entry.

• admin1_ref: Filter the response by a location (typically a country) reference number.

• location_ref: Filter the response by a location (typically a country) reference number.

• code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠.

• name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "id": 1,
      "admin1_ref": 1,
      "code": "string",
      "name": "string",
      "admin1_code": "string",
      "from_cods": true,
      "location_ref": 1,
      "admin1_name": "string",
      "reference_period_start": "2024-01-01T12:00:00Z",
      "reference_period_end": "unknown_type",
      "location_code": "string",
      "location_name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_currency_get

Provide currency information to use in conjunction with the food-prices endpoint

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• code: Filter the response by the currency code.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "code": "string",
      "name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_data_availability_get

Provide currency information to use in conjunction with the food-prices endpoint

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• category: Filter the response by a data category

• subcategory: Filter the response by a data subcategory

• hapi_updated_date_min: Minimum date that datasets was last updated, e.g. 2020-01-01 or 2020-01-01T00:00:00

• hapi_updated_date_max: Maximum date that datasets was last updated, e.g. 2020-01-01 or 2020-01-01T00:00:00

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "subcategory": "string",
      "hapi_updated_date": "unknown_type",
      "admin2_name": "unknown_type",
      "admin1_name": "unknown_type",
      "category": "string",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_dataset_get

Get information about the HDX Datasets⁠ that are used as data sources for HDX HAPI. Datasets contain one or more resources, which are the sources of the data found in HDX HAPI.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• dataset_hdx_id: Filter the response by the dataset ID (dataset_hdx_id), which is a unique and fixed identifier of a Dataset on HDX. A URL in the pattern of https://data.humdata.org/dataset/[dataset_hdx_id] will load the dataset page on HDX.

• dataset_hdx_stub: Filter the response by the URL-safe name (dataset_hdx_stub) of the dataset as displayed on HDX. This name is unique but can change. A URL in the pattern of https://data.humdata.org/dataset/[dataset_hdx_stub] will load the dataset page on HDX.

• dataset_hdx_title: Filter the response by the title of the dataset as it appears in the HDX interface. This name is not unique and can change.

• hdx_provider_stub: Filter the response by the URL-safe name of the provider (organization) of the dataset on HDX. A URL in the pattern of https://data.humdata.org/organization/[hdx_provider_stub] will load the provider's page on HDX.

• hdx_provider_name: Filter the response by the display name of the provider (organization) of the dataset on HDX.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "dataset_hdx_id": "string",
      "dataset_hdx_stub": "string",
      "dataset_hdx_title": "string",
      "hdx_api_link": "string",
      "provider_hdx_api_link": "string",
      "provider_hdx_link": "string",
      "hdx_link": "string",
      "hdx_provider_name": "string",
      "hdx_provider_stub": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_location_get

Not all data are available for all locations. Learn more about the scope of data coverage in HDX HAPI in the Overview and Getting Started⁠ documentation.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• id: Filter the response by a location (typically a country) reference number.

• code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes.

• name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "id": 1,
      "code": "string",
      "name": "string",
      "reference_period_end": "unknown_type",
      "from_cods": true,
      "in_gho": true,
      "has_hrp": true,
      "reference_period_start": "2024-01-01T12:00:00Z"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_org_get

Get the list of organizations represented in the data available in HDX HAPI

🔄 Pagination: You can page through results using limit and offset parameters (limit=records per page, offset=starting position).

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• acronym: Filter the response by the standard acronym used to represent the organization. When data is brought into the HDX HAPI database, an attempt is made to standardize the acronyms.

• name: Filter the response by the standard name used to represent the organization. When data is brought into the HDX HAPI database, an attempt is made to standardize the acronyms.

• org_type_code: Filter the response by the organization type code.

• org_type_description: Filter the response by the organization type description. Use the metadata_org_type_get tool to get available organization type codes and descriptions.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "acronym": "string",
      "name": "string",
      "org_type_code": "unknown_type",
      "org_type_description": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_org_type_get

There is no agreed standard for the classification of organizations. The codes and descriptions used in HDX HAPI are based on this dataset⁠.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• code: Filter the response by the organization type code.

• description: Filter the response by the organization type description.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "code": "string",
      "description": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_resource_get

Get information about the resources that are used as data sources for HDX HAPI. Datasets contain one or more resources, which are the sources of the data found in HDX HAPI.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• resource_hdx_id: Filter the response by the resource ID, which is a unique and fixed identifier of a resource on HDX. A URL in the pattern of https://data.humdata.org/dataset/[dataset_hdx_id]/resource/[resource_hdx_id] will load the resource page on HDX.

• format: Filter the response by the format of the resource on HDX. These are typically file formats (i.e. CSV, XLSX), but can also include APIs and web apps.

• update_date_min: Minimum date that datasets was last updated, e.g. 2020-01-01 or 2020-01-01T00:00:00

• update_date_max: Maximum date that datasets was last updated, e.g. 2020-01-01 or 2020-01-01T00:00:00

• is_hxl: Filter the response by whether or not the resource contains HXL tags⁠.

• dataset_hdx_id: Filter the response by the dataset ID (dataset_hdx_id), which is a unique and fixed identifier of a dataset on HDX. A URL in the pattern of https://data.humdata.org/dataset/[dataset_hdx_id] will load the dataset page on HDX. Use the metadata_dataset_get tool to get available dataset information.

• dataset_hdx_stub: Filter the response by the URL-safe name (dataset_hdx_stub) of the dataset as displayed on HDX. This name is unique but can change. A URL in the pattern of https://data.humdata.org/dataset/[dataset_hdx_stub] will load the dataset page on HDX. Use the metadata_dataset_get tool to get available dataset information.

• dataset_hdx_title: Filter the response by the title of the dataset as it appears in the HDX interface. This name is not unique and can change. Use the metadata_dataset_get tool to get available dataset information.

• dataset_hdx_provider_stub: Filter the response by the URL-safe name of the provider (organization) of the dataset on HDX. A URL in the pattern of https://data.humdata.org/organization/[dataset_hdx_provider_stub] will load the provider's page on HDX.

• dataset_hdx_provider_name: Filter the response by the display name of the provider (organization) of the dataset on HDX.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "resource_hdx_id": "string",
      "dataset_hdx_id": "string",
      "name": "string",
      "dataset_hdx_link": "string",
      "hdx_api_link": "string",
      "download_url": "string",
      "update_date": "2024-01-01T12:00:00Z",
      "dataset_hdx_provider_name": "string",
      "hapi_updated_date": "2024-01-01T12:00:00Z",
      "provider_hdx_api_link": "string",
      "is_hxl": true,
      "dataset_hdx_stub": "string",
      "hdx_link": "string",
      "dataset_hdx_provider_stub": "string",
      "dataset_hdx_title": "string",
      "provider_hdx_link": "string",
      "format": "string",
      "dataset_hdx_api_link": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_sector_get

There are a variety of standards for the naming of humanitarian sectors. The codes and descriptions used in HDX HAPI are based on this dataset⁠.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• code: Filter the response by the sector code.

• name: Filter the response by the sector name.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "code": "string",
      "name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_wfp_commodity_get

Provide commodity information to use in conjunction with the food-prices endpoint

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• code: Filter the response by the unique code identifying the commodity.

• category: Filter the response by the food group that the commodity belongs to, available values are described here.⁠

• name: Filter the response by the name of the commodity.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "code": "string",
      "category": "cereals and tubers",
      "name": "string"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: metadata_wfp_market_get

Provide physical market location information to use in conjunction with the food-prices endpoint

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• code: Filter the response by the unique code identifying the market.

• name: Filter the response by the name of the market.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin2_code: Filter the response by the 2nd subnational administrative divisions. The admin2 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin2_name: Filter the response by the 2nd subnational administrative divisions. The admin2 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin2_get tool to get available admin2 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "code": "string",
      "admin_level": 1,
      "name": "string",
      "lon": "unknown_type",
      "admin2_name": "unknown_type",
      "lat": "unknown_type",
      "admin1_name": "unknown_type",
      "admin2_code": "unknown_type"
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: poverty_rate_get

Poverty rate data from the Oxford Department of International Development. See the more detailed technical HDX HAPI documentation⁠, and the Oxford Department of International Development⁠ website.

Query Parameters:

• app_identifier (Required): base64 encoded application name and email, as in base64("app_name:email"). This value can also be passed in the X-HDX-HAPI-APP-IDENTIFIER header. See the encoded_app_identifier endpoint.

• mpi_min: Multidimensional Poverty Index (MPI), lower bound.

• mpi_max: Multidimensional Poverty Index (MPI), upper bound.

• has_hrp: Filter the response by the has_hrp flag. The has_hrp flag indicates whether a country has a Humanitarian Response Plan.

• in_gho: Filter the response by the in_gho flag. The in_gho flag indicates whether a country is in the Global Humanitarian Overview⁠.

• start_date: Filter entries to include rows where the reference period overlaps with or extends beyond this date, e.g. 2020, 2020-01, 2020-01-01 or 2020-01-01T00:00:00

• end_date: Filter entries to include rows where the reference period overlaps with or begins prior to this date, e.g. 2020, 2020-01, 2020-01-01, 2020-01-01 or 2020-01-01T23:59:59

• location_code: Filter the response by a location (typically a country). The location codes use the ISO-3 (ISO 3166 alpha-3) codes. Use the metadata_location_get tool to get available location codes and names.

• location_name: Filter the response by a location (typically a country). The location names are based on the "short name" from the UN M49 Standard⁠. Use the metadata_location_get tool to get available location codes and names.

• admin1_code: Filter the response by the 1st subnational administrative divisions. The admin1 codes refer to the p-codes in the Common Operational Datasets⁠. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin1_name: Filter the response by the 1st subnational administrative divisions. The admin1 names refer to either the Common Operational Datasets⁠ or those provided in the original data source. Use the metadata_admin1_get tool to get available admin1 codes and names.

• admin_level: Filter the response by admin level.

• output_format: No description.

• limit: Maximum number of records to return. The system will not return more than 10,000 records.

• offset: Number of records to skip in the response. Use in conjunction with the limit parameter to paginate.

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "data": [
    {
      "location_code": "string",
      "location_name": "string",
      "admin1_code": "unknown_type",
      "admin_level": 1,
      "intensity_of_deprivation": "unknown_type",
      "reference_period_end": "unknown_type",
      "mpi": 1.5,
      "headcount_ratio": 1.5,
      "in_severe_poverty": 1.5,
      "admin1_name": "unknown_type",
      "resource_hdx_id": "string",
      "reference_period_start": "unknown_type",
      "vulnerable_to_poverty": 1.5
    }
  ]
}

• 400: Bad Request

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": "string"
}

• 422: Validation Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "detail": [
    {
      "loc": [
        "unknown_type"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

• 500: Internal Server Error

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "error_sample_list": [
    "unknown"
  ],
  "error": "string"
}

Tool: util_version_get

Display the API and SQL Alchemy versions

🔄 Pagination: You can page through results using limit and offset parameters (limit=records per page, offset=starting position).

Responses:

• 200 (Success): Successful Response

  • Content-Type: application/json

  • Response Properties:

  • Example:

{
  "api_version": "string",
  "hapi_sqlalchemy_schema_version": "string"
}

Use this MCP Server

{
  "mcpServers": {
    "hdx": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HDX_APP_IDENTIFIER",
        "mcp/hdx"
      ],
      "env": {
        "HDX_APP_IDENTIFIER": "<HDX_APP_IDENTIFIER>"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠