API archive entry · source-reported
Harry Potter API
API to get data from Harry Potter books, movies, characters and spells
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
PotterAPI is a Harry Potter API developed with Express.js and available in multiple languages. This API stores information and images of books, characters and spells. Explore the API and its endpoints interactively using our Harry Potter API Documentation. This API is available in the following languages: If there's any problem with the translations, you can open an issue or a pull request. The endpoints are the following: Note: The [lang] in the endpoint should be replaced by the corresponding language reference without the brackets (GET /en/books for example) You have to change the [lang] by one of the two-letter codes of the languages supported. Every endpoint has a /random, which returns a random item of the full list. For example /en/spells/random returns a single random spell in English. Every endpoint (excluding the /randoms) can recieve the following query params: Param | Recieves | Description | ----- | -------- | -----------…
Read the full README ↗ · Preview checked 2026-09-20T18:30:13.564Z
Inside the original README — Document outline
- PotterAPI
- Live Documentation (Swagger UI)
- Languages
- Endpoints
- Params
- Examples
- Javascript
- Python
- Running locally
- Clone Repo:
- Run in dev mode
- Test
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from Public API Lists. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Sep 20, 2026
- Last directory-field change: Sep 20, 2026
- Current source observation: Sep 20, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.