Asylum applications, by origin and asylum country

Name: Asylum applications, by origin and asylum country
Creator: UNHCR — Refugee Population Statistics Database
License: https://www.unhcr.org/what-we-do/data-and-publications/data-and-statistics/terms-use-datasets
Keywords: refugees, asylum, migration, unhcr

Annual asylum claims (applications for international protection) by country of origin and country of asylum, broken down by the provider's procedure dimensions: procedure type (authority the claim was lodged with: Government, Joint, UNHCR), application type (stage of the procedure: New, Repeat, Appeal), decision level, and whether the count reflects cases or persons.

Source: UNHCR — Refugee Population Statistics Database120,597 rowsUpdated: 9/22/2026License: CC-BY-4.0

refugeesasylummigrationunhcr

Quality

100

Attribution

UNHCR Refugee Population Statistics Database

Schema

Column	Type	Description
date	timestamp	Reference year of the observation, mapped to January 1 of that year. UNHCR's population data are end-of-year figures; applications, decisions and solutions are annual totals for the reference year.
coo_name	string	Country of origin name (provider's wording).
coo	string	Country of origin UNHCR code.
coo_iso	string	Country of origin ISO code.
coa_name	string	Country of asylum name (provider's wording).
coa	string	Country of asylum UNHCR code.
coa_iso	string	Country of asylum ISO code.
procedure_type	string	The procedure type describes the authority with whom the asylum claim was lodged. It can be one of: G – Government, J – Joint, U – UNHCR.
app_type	string	The application type describes the stage of the procedure. Common values are N (New), R (Repeat) and A (Appeal).
dec_level	string	The decision level provides more detail of the stage of the procedure. Common values are NA (New applications), RA (repeat/reopened applications) and AR (administrative review).
app_pc	string	The data type describes whether the data provided reflects cases or persons. The most common situation is for the data on asylum applications lodged to reflect persons, but in certain situations (e.g. USA), the data provided by governments is at the level of cases. A case can contain information on one or more persons.
series_id	string	Stable machine identifier built from the provider's own codes: UNHCR country-of-origin code, country-of-asylum code, and the measure or procedure-dimension codes (e.g. "AFG.AUL.refugees", "AFG.AUL.G.A.AR.C" for an asylum-applications row).
series_label	string	Human-readable series name using the provider's own country names, e.g. "Afghanistan → Australia — Refugees".
unit	string	"persons": all measures are counts of people. For asylum applications/decisions the provider notes the data usually reflects persons but governments sometimes report cases (see app_pc/dec_pc); a case can contain one or more persons.
value	integer	Observed count. The provider marks missing observations with "-"; these become null and are dropped from the canonical frame.

Sample rows

date	coo_name	coo	coo_iso	coa_name	coa	coa_iso	procedure_type	app_type	dec_level	app_pc	series_id	series_label	unit	value
2015-01-01T00:00:00	Afghanistan	AFG	AFG	Albania	ALB	ALB	G	N	FI	P	AFG.ALB.G.N.FI.P	Afghanistan → Albania — new asylum applications (G/N/FI)	persons	5
2016-01-01T00:00:00	Afghanistan	AFG	AFG	Albania	ALB	ALB	G	N	FI	P	AFG.ALB.G.N.FI.P	Afghanistan → Albania — new asylum applications (G/N/FI)	persons	64
2017-01-01T00:00:00	Afghanistan	AFG	AFG	Albania	ALB	ALB	G	N	FI	P	AFG.ALB.G.N.FI.P	Afghanistan → Albania — new asylum applications (G/N/FI)	persons	29
2018-01-01T00:00:00	Afghanistan	AFG	AFG	Albania	ALB	ALB	G	N	FI	P	AFG.ALB.G.N.FI.P	Afghanistan → Albania — new asylum applications (G/N/FI)	persons	36
2019-01-01T00:00:00	Afghanistan	AFG	AFG	Albania	ALB	ALB	G	N	FI	P	AFG.ALB.G.N.FI.P	Afghanistan → Albania — new asylum applications (G/N/FI)	persons	5

Download sample data

Download the full sample snapshot for this dataset (sample rows, not the complete dataset).

Download sample CSV Download sample JSON

Use with an LLM

Point any LLM at the metadata endpoint — the documentation above is machine-readable too (JSON-LD + Croissant).

cURL

curl "https://datazimuts.com/v1/datasets/unhcr/unhcr_asylum_applications" | jq '{title, rows, columns_count, license}'

Python

import requests

ds = requests.get("https://datazimuts.com/v1/datasets/unhcr/unhcr_asylum_applications").json()
print(ds["title"], ds["rows"], "rows")

# Sample rows for an LLM context window
for row in ds.get("sample_rows", [])[:5]:
    print(row)

API endpoint: https://datazimuts.com/v1/datasets/unhcr/unhcr_asylum_applications

Tip: fetch /llms.txt for the full machine-readable catalog.