Mobbin APImobbin.com ↗
Access Mobbin's UI/UX design flows, screen patterns, and screenshots via API. Browse categories, search flows, and retrieve annotated screens for mobile and web.
What is the Mobbin API?
The Mobbin API exposes 4 endpoints for browsing and searching UI/UX design flows across mobile and web platforms. The list_flows endpoint returns categorized flow types with slugs, counts, and preview screenshots; get_flow_details delivers individual flows with per-screen annotations, app metadata, and screenshot URLs; get_screens retrieves screens filtered by pattern and element type, covering app names, descriptions, and pattern tags.
curl -X GET 'https://api.parse.bot/scraper/945ab7a7-80c0-42fc-80d1-0278c40a86d0/list_flows?platform=web' \ -H 'X-API-Key: $PARSE_API_KEY'
List all flow categories and their flow types for a given platform. Returns categories (e.g., Account Management, Commerce & Finance) with flow type tags, counts, slugs, and preview screenshots. The web platform provides full category data with flow counts; the mobile platform provides a flat list of available flow types.
| Param | Type | Description |
|---|---|---|
| platform | string | Platform type. Accepted values: 'mobile', 'web'. |
{
"type": "object",
"fields": {
"platform": "string, the platform queried",
"categories": "array of category objects, each with title and flow_types containing tag, slug, flow_count, and preview_screens",
"total_categories": "integer, total number of categories",
"total_flow_types": "integer, total number of flow types across all categories"
},
"sample": {
"data": {
"platform": "web",
"categories": [
{
"title": "Account Management",
"flow_types": [
{
"tag": "Logging In",
"slug": "logging-in",
"flow_count": 703,
"preview_screens": [
{
"id": "e2d2bf98-cd9d-433a-8ce2-6018d122e5ef",
"app_name": "Jira",
"image_url": "https://bytescale.mobbin.com/FW25bBB/image/mobbin.com/prod/file.webp?enc=..."
}
]
}
]
}
],
"total_categories": 6,
"total_flow_types": 69
},
"status": "success"
}
}About the Mobbin API
Flow Categories and Discovery
The list_flows endpoint returns the full taxonomy of flow categories — such as Account Management or Commerce & Finance — for either the mobile or web platform. Each category contains an array of flow types with a tag, slug, flow_count, and preview_screens. The response also includes total_categories and total_flow_types counts at the top level. The web platform returns complete category data including flow counts; the mobile platform may return partial data.
The search_flows endpoint accepts a query string and performs case-insensitive substring matching against flow tag names and category titles. Results include the matched category, tag, slug, flow_count, and a url field — making it the right starting point when you want to find the slug for a specific flow type to pass into get_flow_details.
Flow Details and Screen Data
get_flow_details takes a required flow_action slug (e.g., logging-in, adding-to-cart-bag) and returns an array of flow objects. Each flow carries id, name, app_name, app_id, app_logo_url, platform, actions, video_url, and a screens array with per-screen detail. This endpoint is currently reliable only for the web platform.
get_screens focuses on UI screen patterns rather than flows. It requires a screen_pattern slug (e.g., login, checkout, onboarding) and optionally accepts a screen_element filter for substring-matching against element names or slugs. Each returned screen object includes id, screenshot_url, app_name, app_logo_url, screen_name, description, and arrays of screen_patterns and screen_elements — giving structural metadata beyond just the image URL.
The Mobbin API is a managed, monitored endpoint for mobbin.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mobbin.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 mobbin.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 design reference tool that lets users search Mobbin flows by keyword using
search_flowsand browse annotated screenshots. - Aggregate app onboarding flows across multiple products by querying
get_flow_detailswith theonboardingslug. - Catalog checkout UI patterns by platform using
get_screenswithscreen_patternset tocheckout. - Generate a competitive analysis of login screen elements by filtering
get_screenswithscreen_elementset to specific UI components. - Populate a design system library with real-world screenshot references and app metadata from
get_flow_detailsresponses. - Index all available flow categories and their counts via
list_flowsto power a searchable directory of UX patterns. - Track which apps implement specific screen patterns by collecting
app_nameandapp_logo_urlfields fromget_screensresults.
| 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 Mobbin have an official developer API?+
What does `get_screens` return beyond screenshot URLs?+
get_screens returns each screen's id, screenshot_url, app_name, app_logo_url, screen_name, description, and arrays of screen_patterns and screen_elements. The optional screen_element parameter filters results by case-insensitive substring match against element names or slugs, so you can narrow results to screens containing a specific component type.Is `get_flow_details` available for mobile flows?+
mobile platform value, but detailed flow data including per-screen annotations is currently reliable only for the web platform. Mobile results may be incomplete. You can fork this API on Parse and revise it to extend mobile platform coverage once that data becomes consistently available.Does the API return user-curated collections or bookmarks from Mobbin?+
Can I retrieve full video walkthroughs of flows?+
get_flow_details response includes a video_url field per flow object. However, availability of actual video content depends on whether Mobbin has published a video for that specific flow — not all flows include one.