Interpol Red Notices API

Beginner's Pick Government / No Auth Required Beginner HTTPS
Free to Use Varies (check documentation)

Overview

The Interpol Red Notices API provides free access to Interpol's public database of Red Notices, which are international requests to locate and arrest wanted persons. No authentication is required, making it easy to query directly. You can search by name, nationality, and other criteria to build security research tools or awareness applications.

Beginner Tip

The API is hosted at ws-public.interpol.int and is publicly accessible without a key. Start with a simple GET to /notices/v1/red to retrieve the latest notices without any filters.

Available Data

Interpol Red Notices data via REST API

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from Interpol Red Notices",
    "description": "Access and search Interpol Red Notices",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

_embedded.notices Array of Red Notice objects matching the current query and page
forename First name of the wanted person as registered with Interpol
name Surname or family name of the wanted person
nationalities List of nationality codes (ISO 3166-1 alpha-2) associated with the individual
entity_id Unique Interpol identifier for this Red Notice record, usable to fetch full details
_links.self.href URL to retrieve the full detail record for this specific notice

Implementation Example

Request
const url = "https://interpol.api.bund.dev/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Empty _embedded.notices array Filter combination returns no results (e.g., unknown nationality code)
Use the standard ISO 3166-1 alpha-2 country codes for nationality filters and try broadening your search
CORS error in browser The API may restrict direct browser-based requests from unknown origins
Route your requests through a backend server or serverless function to avoid CORS issues
429 Too Many Requests Sending too many requests in a short period
Add delays between requests and cache results locally since the data does not change frequently

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Government
Difficulty Beginner
Verified: 2026-04-04

Similar APIs

View All →