Mobbin APImobbin.com ↗
Access Mobbin's UI/UX design flows via API. Browse flow categories, get detailed screen data with screenshots, and search flows by keyword for mobile and web.
What is the Mobbin API?
The Mobbin API exposes 3 endpoints for querying UI/UX design flows indexed from Mobbin's public explore pages, covering both mobile and web platforms. list_flows returns all flow categories with per-type counts and preview screenshots. get_flow_details returns individual flows including app name, screen patterns, screen elements, and video URLs. search_flows lets you find flow types by keyword across all categories.
curl -X GET 'https://api.parse.bot/scraper/945ab7a7-80c0-42fc-80d1-0278c40a86d0/list_flows?platform=web' \ -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 mobbin-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.
"""Mobbin Flows API — explore UI/UX design flow patterns across web and mobile apps."""
from parse_apis.mobbin_flows_api import Mobbin, Platform, FlowActionNotFound
client = Mobbin()
# List all flow categories for web platform (full data with counts)
for category in client.flowcategories.list(platform=Platform.WEB, limit=3):
print(category.title, len(category.flow_types), "flow types")
# Search for flow types matching a keyword
results = client.flowtypes.search(query="log", platform=Platform.WEB, limit=5)
for ft in results:
print(ft.tag, ft.slug, ft.flow_count)
# Drill into a specific flow type to get detailed flow screens
flow_type = client.flowtypes.search(query="log", platform=Platform.WEB, limit=1).first()
if flow_type:
for flow in flow_type.details(platform=Platform.WEB, limit=3):
print(flow.app_name, flow.name, flow.screen_count)
# Handle flow action not found
try:
bogus = client.flowtype("nonexistent-flow-xyz")
for flow in bogus.details(platform=Platform.WEB, limit=1):
print(flow.name)
except FlowActionNotFound as exc:
print(f"Flow not found: {exc.flow_action}")
print("exercised: flowcategories.list / flowtypes.search / flowtype.details / FlowActionNotFound")
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
What the API Covers
The Mobbin API gives programmatic access to Mobbin's categorized library of real-world UI/UX flow recordings. Two platforms are supported — mobile and web — and every endpoint accepts an optional platform parameter to scope results. list_flows returns an array of categories (for example, "Account Management" or "Commerce & Finance"), each containing its flow types with a tag, slug, flow_count, and preview_screens array.
Getting Flow Details
get_flow_details takes a required flow_action slug (such as logging-in or adding-to-cart-bag) and returns a flows array. Each flow object includes the app_name, app_id, app_logo_url, platform, an actions list, a video_url, and a screens array. Each screen carries pattern and element annotations, making the response useful for analyzing interaction patterns at a granular level. The total_flows field tells you how many flows matched the slug.
Searching Across Flow Types
search_flows accepts a query string and performs case-insensitive substring matching against both flow tag names and category titles. Results include each match's category, tag, slug, flow_count, and a direct url. This is the fastest way to discover which slugs to pass into get_flow_details without manually browsing list_flows. The total_results field shows how many flow types matched.
Scope and Limitations
The API reflects Mobbin's publicly visible explore pages. Data is scoped to flow-level metadata and per-screen annotations; it does not include user-curated collections, individual user profiles, or private saved boards. Flow coverage depends on what Mobbin has indexed for each app, so less common apps may have few or no flows.
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?+
- Audit onboarding flows across competing apps by querying the 'onboarding' slug via get_flow_details and comparing screen counts and patterns.
- Build a design reference tool that maps flow categories from list_flows to annotated screenshots for a given platform.
- Search for checkout flows using search_flows with a query like 'cart' to surface all relevant slugs before pulling full screen data.
- Track how many apps implement a specific flow type by reading the flow_count field returned by list_flows or search_flows.
- Extract app logo URLs and names from get_flow_details to build a competitive landscape of apps covering a specific user action.
- Compare mobile vs. web implementations of the same flow by calling get_flow_details with both platform values and diffing the screen elements.
- Populate a design system database with real-world screen pattern labels sourced from the screens array in get_flow_details.
| 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.