New Features and Enhancements in the V2 API

Note: To use the V2 API, you must place v2 in the call. For example:

  • The API now returns ISO 3 and ISO 2 codes for all the countries along with country name, region, admin region, income level, lending type, Capital City, geographical co-ordinates.
  • The 2-letter codes for Region, admin Region, Income Level and Lending Type are assigned and used by The World Bank.
  • ISO2 code is available for Region, Income Level & Lending Type.


Enhancements in the indicator data queries


The below information is now included in the response:

  • The date(YYYY-mm-dd) of the source’s most recent update.

  • Country ISO3 code: Returns the country’s ISO3 code.

  • Country Code (optional): Returns the country’s 3 character code, if desired. “Ctrycode=y” gives the Worldbank’s 3 character code for the country, region, income level, and/or lending types called. “Ctrycode=n” removes the country code from the response.
  • Footnote (optional): Fetches footnote details in data calls, if desired. “Footnote=y” gives the footnote value for country, indicator and year. “Footnote=n” removes the footnote from the response.
  • Automatic Scale of numbers (optional): Data values will be scaled automatically in thousands, millions, billions or trillions. If the data is less than a thousand, no scaling will be applied. “Scale=y” gives the scale in the response. “Scale=n” removes the scale from the response.
  • Precision: If the user requests for scaling, precision of decimal point will be based on the <wb:decimal> tag value, found in the response. If <wb:decimal> is 1 then the scaled value will have precision up to 1 decimal point. For example, if the data value is 2500 and <wb:decimal> is 1, then the data value will be scaled to 2.5 and <wb:scale> will read “thousands”.
  • Observation Status: Returns the observation status for country, indicator, and year combination. For example, F in the response indicates that the observation status for that data point is "forecast".

Enhancements in JSON responses for indicator data queries


  • Supports native JSON parser.
  • The “fact” data type is now a number.
  • Multiple indicators data: Multiple indicators data can be queried from a particular data source by providing source ID and indicators codes separated by “;” (semicolon).

Local Languages

Some countries are translated in their local languages. Any call to the API can be prefixed with a language code to retrieve localized results. The following local languages are available:

Code Language
bg Bulgarian
de German
hi Hindi
id Indonesian
ja Japanese
km Khmer
ko Korean
mk Macedonian
mn Mongolian
pl Polish
pt Portuguese
ro Romanian
ru Russian
sq Albanian
th Thai
tr Turkish
uk Ukrainian
vi Vietnamese

A backslash followed by the country code gives localized results. For example, to retrieve the country name of Vietnam in Vietnamese language you would use the following query:

Note: The translated local language country names are not available for all the countries.

New JSONstat response format option for indicator data queries (BETA):

JSONstat is a simple lightweight JSON dissemination format best suited for data visualization, mobile apps or open data initiatives that has been designed for all kinds of disseminators. Format=jsonstat’ gives the JSONstat response.


Download Enhancements

Download to CSC or EXCEL Formats

Note: Country metadata will have special notes only for English language.

List or Table Formatting

You can now download indicator data in either List or Table format. The query string “dataformat” is used to download the indicator data into a list, with the years in either rows or columns. This query string works together with the “downloadformat” query string.

Possible query strings for “dataformat”:

  • “Dataformat=table” gives data in table format (column-wise year).
  • “Dataformat=list” gives data in list format (row-wise year).

Example Request:

Example Response:

*Data Format: Table*

Example Request:

Example Response:

*Data Format: List*

New Data Types

Thank you for visiting the World Bank's Data Help Desk. Please review the terms of use for this website. Your continued use of this website constitutes your acceptance of these terms and conditions.

Developer Info

Feedback and Knowledge Base