Police Auctions Canada APIpoliceauctionscanada.com ↗
Access Police Auctions Canada listings via API. Search active auctions, get item details, current bids, bid counts, and items ending within 24 hours.
What is the Police Auctions Canada API?
The Police Auctions Canada API provides 3 endpoints to browse, search, and inspect active Canadian police auction listings. The search_listings endpoint accepts keyword queries and category filters, returning bid counts, current bids, and time remaining per item. get_listing_details exposes per-listing data including images, start and end dates, high bidder status, and full category. list_ending_soon surfaces items closing within 24 hours, paginated and sorted by ending time.
curl -X GET 'https://api.parse.bot/scraper/a59b64c8-708e-4bfe-b8c7-dd1161f8b167/search_listings?page=1&query=bike&category=632998' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace policeauctionscanada-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
Police Auctions Canada API - Browse and search auction listings
"""
from parse_apis.police_auctions_canada_api import PoliceAuctions, ListingSummary, Listing, Category
client = PoliceAuctions()
# Search for electronics auctions
for item in client.listingsummaries.search(query="camera", category=Category.ELECTRONICS, limit=5):
print(item.title, item.current_bid, item.end_time)
# Drill into full details for the listing
details = item.details()
print(details.description, details.high_bidder, details.images)
# Get a specific listing by ID
listing = client.listings.get(listing_id="88437991")
print(listing.title, listing.status, listing.bid_count)
# Browse items ending soon
for soon in client.listingsummaries.ending_soon(limit=3):
print(soon.title, soon.current_bid, soon.bid_count)
Search auction listings by keyword with optional category filter. Returns paginated results with current bid, time remaining, and bid count for each listing. Paginates via integer page number. Omitting query returns all active listings; adding a category ID narrows results to that category.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| query | string | Search keywords to filter listings (e.g. 'bike', 'camera'). Omitting returns all active listings. |
| category | string | Category ID to filter results. |
{
"type": "object",
"fields": {
"page": "current page number",
"listings": "array of ListingSummary objects with listing_id, title, url, current_bid, end_time, bid_count, image_url",
"total_pages": "total number of pages available",
"result_count": "number of listings on this page"
},
"sample": {
"data": {
"page": 1,
"listings": [
{
"url": "https://www.policeauctionscanada.com/Listing/Details/88437991/Norco-21Speed-Shimano-Outfitted-FS-Bike-322744D",
"title": "Norco 21-Speed Shimano Outfitted FS Bike (322744D)",
"end_time": "06/14/2026 22:03:00",
"bid_count": "3",
"image_url": "https://pacimages.blob.core.windows.net/assets/media/f874402e-c51b-4180-a3c7-b09bc8bcf343_thumbfit.jpg",
"listing_id": "88437991",
"current_bid": "6.75"
}
],
"total_pages": 2,
"result_count": 6
},
"status": "success"
}
}About the Police Auctions Canada API
Endpoints and Data Coverage
The API covers three operations against Police Auctions Canada's active inventory. search_listings accepts a query string (e.g. 'bike', 'camera') and an optional category parameter using known category IDs such as 632998 for Art & Antiques, 161051 for Automotive, 161054 for Books, and 568526 for additional categories. Results are paginated and each listing summary includes the current bid, time remaining, and bid count. The page parameter controls pagination, and total_pages plus result_count are returned to help iterate through full result sets.
Listing Details
get_listing_details takes a numeric listing_id — obtainable from either search_listings or list_ending_soon — and returns a richer record: title, images (array of URLs), status, category, start_date, end_date, end_time, bid_count, current_bid, and listing_id. This is the endpoint to use when building item pages or tracking price movement on a specific lot.
Ending-Soon Feed
list_ending_soon returns auction items whose end time falls within the next 24 hours, sorted by closing time. It shares the same paginated response shape as search_listings — listings array, page, total_pages, and result_count. This endpoint is suited for bidding-alert tools and time-sensitive deal monitors that need to surface the most urgent active lots without a keyword filter.
The Police Auctions Canada API is a managed, monitored endpoint for policeauctionscanada.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when policeauctionscanada.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official policeauctionscanada.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a bidding-alert service that polls
list_ending_soonand notifies users when items matching saved keywords are about to close. - Track price history on specific lots by periodically calling
get_listing_detailswith the samelisting_idand recordingcurrent_bidover time. - Aggregate active automotive listings by passing category ID
161051tosearch_listingsto populate a vehicle-focused auction browser. - Monitor bid competition by comparing
bid_countfrom repeated calls toget_listing_detailson a set of watched listings. - Power a deal-discovery feed that surfaces all active listings ending in 24 hours using
list_ending_soonacross multiple pages. - Catalog auction images by collecting the
imagesarray fromget_listing_detailsfor each active listing ID.
| 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 | 100 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 Police Auctions Canada offer an official developer API?+
What does `get_listing_details` return beyond what `search_listings` includes?+
get_listing_details adds images (an array of image URLs), start_date, end_date, end_time, status, and full category text — fields not present in the listing summaries returned by search_listings or list_ending_soon, which focus on bid counts, current bids, and time remaining.Can I filter `list_ending_soon` by category or keyword?+
list_ending_soon only accepts a page parameter. It does not support keyword or category filtering. For filtered results, use search_listings with a query string or category ID. You can fork this API on Parse and revise it to add category or keyword filtering to the ending-soon endpoint.Does the API expose bidder identity or full bid history for a listing?+
get_listing_details returns a bid_count and reflects the current high bidder status, but does not expose individual bidder identities or a timestamped bid history log. The API covers current bid state and item metadata. You can fork it on Parse and revise to add a bid-history endpoint if that data becomes accessible.Are there known category IDs I can pass to `search_listings`?+
632998 (Art & Antiques), 161051 (Automotive), 161054 (Books), and 568526. Other category IDs may exist on the site but are not enumerated in the current API spec. Omitting the category parameter returns results across all active categories.