On this page
MeowLoad Developer API Documentation
This documentation covers the current version (v1) of the API. If you are still using the legacy, unversioned API (/openapi/…), its documentation is on GitHub at Media-Downloader-API, and the migration guide is Migrating from the legacy API.
🚀 Quick Start
The MeowLoad developer API v1 can be used in two ways, with the same API key and the same billing:
- REST API: every endpoint lives under
https://api.meowload.net/openapi/v1, requests and responses are JSON, and authentication is a singleAuthorization: Bearer <your API key>header. - MCP: a hosted MCP server at
https://api.meowload.net/mcp. Once configured, Claude Code, Codex, Cursor and other AI agents can call the API directly, with no code required.
Get Your API Key
Before getting started, please visit the Developer Console to obtain your API Key.
Start with the Quickstart; a single curl call gets you going. To skip the code entirely, see MCP.
📚 API Reference
Core APIs
| Endpoint | Description | API reference |
|---|---|---|
| Single post extraction | Extract individual videos, images, music, and other media content | POST /extract/post |
| Playlist extraction | Batch extract content from profiles, playlists, channels, and topics | POST /extract/playlist |
| Subtitle extraction | Extract video subtitles (supports multiple formats) | POST /extract/subtitles |
| Available credits | Query remaining available API call credits | GET /credits |
Only successful calls (HTTP 200) are charged. The billing rules are listed in the Developer Console.
Code Examples
Complete examples in Python, JavaScript, PHP and Golang:
Next steps
- Quickstart: get an API key, send your first request, and read the response and error body
- API reference: full parameters and response fields of the four endpoints, with a try-it console
- Errors: the 18 extraction error codes and what
retryablemeans - MCP: call the API from Claude Code, Codex or Cursor
- Code examples: Python, JavaScript, PHP and Golang
- Migrating from the legacy API: field rename tables and a migration checklist from the legacy API to v1