Amanaimages APIamanaimages.com ↗
Search amanaimages.com stock photos, illustrations, and video clips by keyword. Returns asset IDs, titles, license types (RF/RM), author credits, and preview URLs.
What is the Amanaimages API?
The amanaimages.com API provides two endpoints — search_images and search_footage — covering the site's still photo/illustration and video clip catalogs. A single search_images call returns up to 100 assets per page, each with a site image ID, title, RF or RM license classification, author credit, thumbnail URL, and detail page URL. search_footage adds a preview MP4 URL and poster thumbnail for each video clip.
curl -X GET 'https://api.parse.bot/scraper/e709b6ee-d00c-4dea-a89d-99a5e35b2c42/search_footage?keyword=%E6%9D%B1%E4%BA%AC' \ -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 amanaimages-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.
"""Walkthrough: amanaimages stock search — images and footage, bounded."""
from parse_apis.amanaimages_com_api import AmanaImages, Sort, InputFormatInvalid
client = AmanaImages()
# Search still images for a keyword, capped at 5 results.
for image in client.images.search(keyword="東京", sort=Sort.RECOMMENDED, limit=5):
print(image.id, image.title, image.license)
# Drill into footage: take the first clip matching a keyword.
try:
clip = client.clips.search(keyword="桜", sort=Sort.NEWEST, limit=1).first()
except InputFormatInvalid as e:
print("Invalid input:", e.message)
clip = None
if clip is not None:
print(clip.title, clip.author)
print("preview:", clip.preview_video_url)
print("detail:", clip.detail_url)
print("exercised: images.search / clips.search")
Searches the amanaimages stock footage (video) catalog by keyword and returns one page of clips. Each item carries the site's clip ID (e.g. one shape: M1045300174), title, license type (RF or RM), author/credit, poster thumbnail URL, preview MP4 URL and the site's detail page URL. One request per call. Pagination is caller-controlled through page and per_page (50 or 100 per page); total_results is the site's full hit count while total_pages is the number of pages the site actually serves (it caps browsing at 9,600 results, so has_more reflects that reachable boundary, not total_results). sort picks the site's recommended or newest ordering. A keyword with no hits returns total_results 0 and an empty items array. Titles may be Japanese or English as stored by the site; keywords must be encodable in Shift_JIS (Japanese and ASCII).
| Param | Type | Description |
|---|---|---|
| page | integer | 1-based result page number; must not exceed total_pages. |
| sort | string | Result ordering. |
| keywordrequired | string | Search keyword (Japanese or English), e.g. 東京. Space-separated words are ANDed by the site. |
| per_page | integer | Clips per page; the site accepts exactly 50 or 100, other values are rejected. |
{
"type": "object",
"fields": {
"page": "integer page returned",
"sort": "ordering applied",
"items": "array of clips: id (site clip ID string), title, license (RF|RM), author, credit, thumbnail_url, preview_video_url (MP4), detail_url",
"keyword": "echo of the searched keyword",
"has_more": "boolean, true when page < total_pages",
"per_page": "integer page size requested",
"total_pages": "integer, number of pages the site serves at this page size (capped by the site)",
"total_results": "integer, the site's total hit count for the keyword"
},
"sample": {
"data": {
"page": 1,
"sort": "recommended",
"items": [
{
"id": "M1045300174",
"title": "tokyo japan city rainbow bridge skyline harbour",
"author": "dubassy",
"credit": "(c) dubassy /amanaimages",
"license": "RF",
"detail_url": "https://amanaimages.com/info/infoMotionRF.aspx?SearchKey=M1045300174&GroupCD=0&no=0&aid=",
"thumbnail_url": "https://p5iconsp.s3-accelerate.amazonaws.com/045300174_iconl.webp",
"preview_video_url": "https://p5resellerp.s3-accelerate.amazonaws.com/045300174.mp4"
}
],
"keyword": "東京",
"has_more": true,
"per_page": 50,
"total_pages": 192,
"total_results": 217876
},
"status": "success"
}
}About the Amanaimages API
What the API Covers
The amanaimages.com API exposes two catalog search endpoints. search_images targets the still photography and illustration catalog; search_footage targets the video/motion clip catalog. Both accept Japanese or English keywords, and space-separated terms are treated as AND queries by the site. Results include the site's native asset ID (e.g. 10889001994 for images, M1045300174 for clips), a title, a license field indicating RF (royalty-free) or RM (rights-managed), and author/credit attribution fields.
Pagination and Page Size
Both endpoints return paginated results with total_results, total_pages, page, per_page, and a has_more boolean. For search_footage, the per_page parameter accepts exactly 50 or 100; other values are rejected by the site. For search_images, the page size is fixed at 100 slots by the site and is reflected in the per_page response field. The page parameter is 1-based and should not exceed total_pages. Both endpoints also echo back the keyword and sort values used.
Preview and Detail URLs
search_images items include a thumbnail_url for preview display and a detail_url linking to the asset's page on amanaimages.com. search_footage items additionally carry a preview_video_url (MP4 format) and a separate thumbnail_url poster image, making it straightforward to build lightweight clip-preview interfaces without a separate lookup step.
Sorting and Coverage
Both endpoints accept an optional sort parameter to control result ordering. The site's total hit count for a keyword is exposed as total_results, but the number of pages actually navigable is capped by the site itself, so very large result sets may not be fully traversable page by page.
The Amanaimages API is a managed, monitored endpoint for amanaimages.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when amanaimages.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 amanaimages.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 bilingual (Japanese/English) stock asset search interface surfacing RF vs. RM license distinctions from the
licensefield. - Aggregate amanaimages clip metadata — including preview MP4 URLs — for a video asset discovery tool.
- Cross-reference
authorandcreditfields fromsearch_imagesresults to track photographer or agency coverage across keywords. - Automate keyword-based catalog audits comparing
total_resultsacross terms to identify content gaps. - Render inline video previews using
preview_video_urlfromsearch_footagefor a production asset management dashboard. - Monitor licensing mix (RF vs. RM ratio) for a given subject keyword by iterating pages and tallying
licensevalues. - Populate a curated editorial image gallery by keyword, using
thumbnail_urlanddetail_urlfromsearch_imagesfor deep-link attribution.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does amanaimages.com have an official developer API?+
How do the two endpoints differ in what they return?+
search_footage returns video clip assets and includes both a preview_video_url (MP4) and a thumbnail_url poster image per item, along with a per_page parameter that accepts 50 or 100. search_images covers still photos and illustrations, has a fixed page size of 100 set by the site, and does not include a video URL — only thumbnail_url and detail_url.Is there a limit on how deep into results I can paginate?+
total_results and total_pages, but the site caps the number of navigable pages regardless of how large total_results is. Requests with a page value exceeding total_pages are not valid. For very high-volume keywords, only a subset of the full result set is reachable through pagination.Can I filter results by license type (RF or RM) before fetching them?+
license field (RF or RM) is returned per item in both search_images and search_footage responses, but neither endpoint accepts a license-type filter as an input parameter. You can fork this API on Parse and revise it to add a license filter input that post-filters or adjusts the query.Does the API return pricing or download/licensing transaction data?+
detail_url field. You can fork this API on Parse and revise it to add an endpoint that retrieves additional detail-page fields.