Postman API Network Scraper avatar

Postman API Network Scraper

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Postman API Network Scraper

Postman API Network Scraper

Scrape the Postman Public API Network - search public collections, workspaces, and API publishers, browse by curated category, or list everything published by a given publisher. No auth, no proxy required.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Scrape the Postman Public API Network — the directory of publicly shared Postman collections, workspaces, and API publishers (Stripe, PayPal, Twilio, and thousands more). Search by keyword, browse by curated category, or list everything a given publisher has shared. No auth, no proxy, no cookies required.

What this actor does

  • Three modes: search, byCategory, byPublisher
  • Search across collections, workspaces, and publisher profiles by free-text query
  • Sort search results by relevance, most-viewed, or recently-updated
  • Browse any of the 12 curated Postman API Network categories (Payments, AI, DevOps, etc.)
  • List every public collection and workspace published by a given team/publisher handle
  • Fork / view / watch counts and endpoint counts on every collection
  • Empty fields are omitted

Output per item

  • itemTypecollection, workspace, or publisher
  • name, summary, description
  • categories[]
  • publisherName, publisherHandle, publisherVerified, publisherLogo
  • endpointCount — number of API requests in the collection (mode=search only)
  • forkCount, viewCount, watchCount
  • forkCountLast30Days, viewCountLast30Days, watchCountLast30Days — trailing-30-day engagement (byCategory/byPublisher modes only)
  • collectionCount, workspaceCount, apiCount — child-entity counts on workspace/publisher records (mode=search only)
  • workspaceName (mode=search only), workspaceSlug
  • tags[]
  • updatedAt, createdAt
  • sourceUrl — canonical postman.com detail page
  • recordType: "postmanApiNetworkItem", scrapedAt

Input

FieldTypeDefaultDescription
modestringsearchsearch / byCategory / byPublisher
searchQuerystringstripeFree-text query (mode=search)
contentTypestringallRestrict search to collection / workspace / publisher
sortBystringrelevancerelevance / mostViewed / recentlyUpdated (mode=search only)
categorystringpaymentsCurated category slug (mode=byCategory)
publisherHandlestringPublisher/team handle, e.g. apilayer (mode=byPublisher)
minForkCountintDrop items with fewer forks than this. Only applies to collection/workspace items — publisher items (teams) have no fork count on Postman's platform and always pass this filter
maxItemsint30Hard cap (1–500)

Example: search for weather APIs

{
"mode": "search",
"searchQuery": "weather",
"contentType": "collection",
"maxItems": 50
}

Example: browse the Payments category

{
"mode": "byCategory",
"category": "payments",
"maxItems": 50
}

Example: everything APILayer has published

{
"mode": "byPublisher",
"publisherHandle": "apilayer",
"maxItems": 100
}

Use cases

  • API discovery — find ready-to-fork Postman collections for a third-party API before writing an SDK
  • Competitive intelligence — track how many collections/forks/views a competitor's API workspace has
  • Developer relations — audit what your organization has published to the API Network and how it's trending
  • Category research — see which providers dominate a vertical (Payments, AI, Travel, etc.)
  • Documentation aggregation — bulk-collect collection descriptions and endpoint counts for a market map

FAQ

What's the Postman API Network? A public directory where teams publish Postman collections/workspaces so other developers can fork them and start calling an API immediately. See postman.com/explore.

Do I need a Postman account or API key? No. All data comes from Postman's own public, unauthenticated JSON endpoints — the same ones the postman.com website itself calls.

What's the difference between a collection, a workspace, and a publisher? A collection is a set of API requests (the "endpoints"). A workspace is a container that groups one or more collections plus docs/environments. A publisher is the team/organization account that owns them.

Why do some items have no endpointCount? Request counts are only returned by mode=search's collection results; the category/publisher listing endpoints don't include them. mode=search's workspace and publisher-profile results instead expose collectionCount/workspaceCount/apiCount.

How do I find a publisher's handle? It's the first path segment of their postman.com URL — e.g. postman.com/apilayer → handle apilayer. You can also discover handles from the publisherHandle field of search or byCategory results.

How fresh is the data? Real-time — every mode reads directly from Postman's live API, the same data the website shows.