Freelance-gig pricing and market research
Use Fiverr endpoints to turn freelance-gig pricing and market research into repeatable API requests with documented inputs and JSON responses.
Turn public Fiverr pages into structured freelance-gig data — keyword gig search, one gig's full detail (pricing packages, rating, tags, gallery), and seller profiles (level, verification, hourly rate, languages), as normalized JSON. Credential-free.
Search Fiverr gigs and get gig detail and seller profiles back as structured JSON.
Endpoint families
3
Documented params
8
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
7
Schema refs
3
{
"platform": "Fiverr",
"endpoint": "fiverr-search",
"method": "GET",
"path": "/fiverr/search",
"auth": "apiKey"
}Use cases
Search Fiverr gigs and get gig detail and seller profiles back as structured JSON.
Use Fiverr endpoints to turn freelance-gig pricing and market research into repeatable API requests with documented inputs and JSON responses.
Use Fiverr endpoints to turn gig listing aggregation and monitoring into repeatable API requests with documented inputs and JSON responses.
Use Fiverr endpoints to turn seller sourcing and vetting into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Fiverr endpoint catalog — 3 endpoints, 8 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented Fiverr endpoints, grouped into 3 request families — Gig, Search and Seller.
8 request parameters are documented across those Fiverr endpoints, 7 of them required — the full input contract is public before you write any integration code.
3 of the 3 Fiverr endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
Fiverr endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the Fiverr endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/fiverr/gig/{username}/{slug}
/fiverr/search
/fiverr/seller/{username}
Endpoint catalog
/fiverr/searchSearches Fiverr's public gig listings by free-text keyword, returning normalized gig summaries (title, seller username, seller level, rating, review count, starting price, category, thumbnail image). Public data sourced from Fiverr's own server-rendered search pages via a real browser-rendering backend. Seller level uses the same values on the search, seller and gig endpoints: level_one_seller, level_two_seller, top_rated_seller, or new_seller.
Response notes
- `seller_username` and the trailing path segment of `url` are the two values `GET /fiverr/gig/{username}/{slug}` needs for gig detail lookup — Fiverr gig URLs have no bare-id form. - `seller_level` is one of `level_one_seller`, `level_two_seller`, `top_rated_seller`, or `new_seller`. `/fiverr/search`, `/fiverr/seller/{username}`, and `/fiverr/gig/{username}/{slug}` all use this same scheme, so levels can be joined across endpoints directly. The field is omitted when the page reports no level for the seller. - `starting_price` is already in whole dollars. - A genuine zero-result search returns `gigs: []` with a `200`, distinct from a parser-drift or blocked-page failure, which returns an error instead. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "logo design", "page": 1, "gigs": [ { "id": "24460733", "title": "do modern minimalist logo design for your business", "url": "https://www.fiverr.com/inshape_studio/do-modern-minimalist-logo-design-for-your-business", "seller_username": "inshape_studio", "seller_country": "Bangladesh", "seller_level": "level_two_seller", "rating": 4.9, "review_count": 3421, "starting_price": 10, "image": "https://fiverr-res.cloudinary.com/gig.jpg", "category_id": 2, "sub_category_id": 65 } ] } } ```
MCP tool fiverr_search
/fiverr/gig/{username}/{slug}Returns a normalized Fiverr gig detail page: title, description, category, pricing packages (basic/standard/premium tiers with price and delivery time), rating, review count, orders in queue, tags, gallery images, and a seller summary (level, rating, response time, languages). Public data sourced from Fiverr's own server-rendered gig pages via a real browser-rendering backend. Seller level uses the same values on the search, seller and gig endpoints: level_one_seller, level_two_seller, top_rated_seller, or new_seller.
Response notes
- `packages[].price` is normalized to whole dollars (the underlying page reports it in cents). - `packages[].delivery_days` is derived from the underlying hour count. - `seller.level` is one of `level_one_seller`, `level_two_seller`, `top_rated_seller`, or `new_seller`. `/fiverr/search`, `/fiverr/seller/{username}`, and `/fiverr/gig/{username}/{slug}` all use this same scheme, so levels can be joined across endpoints directly. The field is omitted when the page reports no level for the seller. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "24460733", "url": "https://www.fiverr.com/inshape_studio/do-modern-minimalist-logo-design-for-your-business", "title": "I will do modern minimalist logo design for your business", "description": "I will create a modern, minimalist logo for your brand.", "category_name": "Graphics & Design", "sub_category_name": "Logo Design", "rating": 4.9, "review_count": 3421, "orders_in_queue": 12, "packages": [ {"tier": "Basic", "description": "1 logo concept", "price": 10, "delivery_days": 3}, {"tier": "Standard", "description": "3 logo concepts", "price": 25, "delivery_days": 5}, {"tier": "Premium", "description": "5 logo concepts", "price": 50, "delivery_days": 7} ], "tags": ["logo", "branding"], "images": ["https://fiverr-res.cloudinary.com/gallery1.jpg"], "seller": { "username": "inshape_studio", "display_name": "InShape Studio", "country": "BD", "level": "level_two_seller", "rating": 4.9, "review_count": 3421, "response_time_hours": 1, "languages": ["en"], "description": "Professional logo designer with 10 years experience.", "profile_image": "https://fiverr-res.cloudinary.com/seller.jpg" } } } ```
MCP tool fiverr_gig
/fiverr/seller/{username}Returns a normalized Fiverr seller profile: display name, one-liner title, description, country, seller level, verification status, hourly rate, spoken languages, join date, and the seller's gig ids. Public data sourced from Fiverr's own server-rendered seller profile pages via a real browser-rendering backend. Seller level uses the same values on the search, seller and gig endpoints: level_one_seller, level_two_seller, top_rated_seller, or new_seller.
Response notes
- `level` is one of `level_one_seller`, `level_two_seller`, `top_rated_seller`, or `new_seller`. `/fiverr/search`, `/fiverr/seller/{username}`, and `/fiverr/gig/{username}/{slug}` all use this same scheme, so levels can be joined across endpoints directly. The field is omitted when the page reports no level for the seller. - `hourly_rate` is normalized to whole dollars (the underlying page reports it in cents). - `joined_at` is an RFC3339 timestamp derived from the underlying Unix seconds value. - `gig_ids` are usable with [`GET /fiverr/gig/{username}/{slug}`](fiverr-gig.md) only once paired with each gig's own slug (from a search result). Example response: ```json { "code": 200, "msg": "OK", "data": { "username": "inshape_studio", "url": "https://www.fiverr.com/inshape_studio", "display_name": "InShape Studio", "one_liner_title": "Modern logo design that grows your brand", "description": "Professional logo designer with 10 years experience.", "country": "BD", "level": "level_two_seller", "is_verified": true, "hourly_rate": 25, "languages": ["en", "bn"], "joined_at": "2016-01-01T00:00:00Z", "profile_image": "https://fiverr-res.cloudinary.com/seller.jpg", "approved_gigs_count": 14, "gig_ids": ["24460733", "24460800"] } } ```
MCP tool fiverr_seller
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Company coverage
Fiverr International Ltd. · FVRR
Fiverr is operated by Fiverr International Ltd. (FVRR). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the Fiverr endpoints above.
SEC filings & financials API →How to scrape Fiverr
Crawlora's Fiverr endpoints return gig search, gig detail with tiered packages, and seller profiles as normalized JSON with one API key. The core of Fiverr's data is the package ladder. A gig sells up to three tiers, each with its own price and delivery time. In one top-rated web-scraping gig, the tiers were $100 in 1 day, $200 in 3 days, and $400 in 5 days.
/fiverr/search returns 48 gigs per page with seller_level (level_one_seller, level_two_seller, or top_rated_seller), is_pro, seller_country, rating, review_count, a starting_price in whole dollars, and category and subcategory ids. For web scraping on 2026-09-18, 28 of 48 sellers were Level 2, 11 were Top Rated, and 24 were based in Pakistan. Starting prices ranged from $5 to $300.
Fiverr gig URLs have no bare id, so pass seller_username and the URL's last path segment to /fiverr/gig/{username}/{slug}. You get packages (tier name, description, price, and delivery_days), orders_in_queue, tags, category names, the gallery images, and an embedded seller block with response_time_hours and languages.
/fiverr/seller/{username} returns the one-line title, level, is_pro, is_verified, hourly_rate in dollars, joined_at, approved_gigs_count, and gig_ids. Pair each gig_id with its slug from search to fetch the gig.
Search, /fiverr/seller, and the gig endpoint's seller block all report level with the same four values: level_one_seller, level_two_seller, top_rated_seller, and new_seller. Fiverr's gig page uses its own short codes (LEVEL_TRS for Top Rated), and the API maps them, so you can count or join sellers by level without a lookup table.
FAQ
Call /fiverr/gig/{username}/{slug}. packages lists each tier with its name, description, price in whole dollars, and delivery_days.
orders_in_queue on /fiverr/gig/{username}/{slug} shows the gig's open order queue, and the seller block's response_time_hours shows typical reply time.
No. Fiverr doesn't offer a general-purpose marketplace-data API at all — its only official API offering is a narrow Affiliate API for generating gig-promotion links, which requires affiliate-program approval and returns nothing about gig pricing, ratings, or seller data. Crawlora's Fiverr endpoints return gig search, gig detail with pricing packages, and seller profiles as structured JSON with a single API key, no affiliate approval required.