crash.pmmp.io APIcrash.pmmp.io ↗
Browse, search, and submit PocketMine-MP crash reports via the crash.pmmp.io API. Filter by version, plugin, error type, and more across 4 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/404827ab-e7d0-4f6e-8400-09d317a77703/get_home' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetches the home page content of the PocketMine Crash Archive, including the site title and description.
No input parameters required.
{
"type": "object",
"fields": {
"url": "string, the base URL of the archive",
"title": "string, the site title",
"description": "string, site meta description"
},
"sample": {
"data": {
"url": "https://crash.pmmp.io",
"title": "PocketMine Crash Archive",
"description": "Crash Archive and classifier for PocketMine"
},
"status": "success"
}
}About the crash.pmmp.io API
The crash.pmmp.io API exposes 4 endpoints for interacting with the PocketMine-MP Crash Archive, covering report listing, detail retrieval, and submission. The list_crash_reports endpoint returns paginated results with fields like error message, plugin involvement, PocketMine version, and report URL, and supports filters including cause, plugin, versions, errortype, and jitonly to narrow down relevant crashes.
Browsing and Filtering Crash Reports
The list_crash_reports endpoint returns an array of crash report objects, each containing id, date, version, is_modified, is_fork, plugin, message, involvement, and url. A pagination object accompanies each response with current_page, has_next, has_prev, and total_reports_matching. You can filter by plugin name (case-sensitive), one or more PocketMine-MP versions, error type substring, and plugin involvement level (none, indirect, or direct). The duplicates boolean controls whether duplicate reports appear in results.
Retrieving Full Report Details
The get_crash_report endpoint accepts a numeric id and returns id, url, details, backtrace, error_message, and report_content for that crash. Note that most reports require administrator access — guest requests return a 401 Unauthorized response. This means broad programmatic access to full report content is limited to reports that have been marked publicly accessible.
Submitting Reports
The submit_crash_report endpoint accepts the full crash dump text in the report_text field along with optional name and email fields (email is kept secret). A successful submission returns a report_id, url, and status. This is useful for automating crash report uploads from server monitoring pipelines.
Site Metadata
The get_home endpoint returns the archive's base url, title, and description. This is primarily useful for verifying connectivity or displaying attribution.
- Aggregate crash reports by PocketMine-MP version to track stability regressions across releases
- Filter crash reports by plugin name to identify crashes associated with a specific third-party plugin
- Detect JIT-related crashes by using the
jitonlyfilter onlist_crash_reports - Automate crash report submission from a PocketMine-MP server watchdog using
submit_crash_report - Build a dashboard showing crash frequency by
involvementtype (none, indirect, direct) across versions - Search for known crashes matching a specific error message substring before deploying a plugin update
- Monitor new crash report submissions by polling
list_crash_reportsand tracking the latest IDs
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does crash.pmmp.io have an official developer API?+
What does `list_crash_reports` return, and how granular is the filtering?+
reports array includes id, date, version, is_modified, is_fork, plugin, message, involvement, and url. You can filter simultaneously by cause (plugin involvement level), plugin name, versions array, errortype substring, message keyword, jitonly boolean, and whether to include duplicates. Pagination metadata is returned in a separate pagination object.Can I access the full backtrace and report content for any crash report?+
401 Unauthorized error for guest requests. The get_crash_report endpoint does return backtrace, error_message, report_content, and details fields when access is granted, but broad guest access to full report content is not available through the archive.Does the API expose comment threads or resolution status for crash reports?+
Is there a way to search crash reports by PHP version or server OS?+
list_crash_reports filters cover PocketMine-MP version, plugin name, error type, message keyword, plugin involvement, and JIT status. PHP version or OS filtering is not exposed as a parameter. You can fork this API on Parse and revise it to add those filters if the underlying data supports them.