Read Fiverr gig listings and package prices with one API call
The Fiverr API returns live gig search, gig detail and public seller profiles as clean JSON, with no login.
4 active endpoints, on 2 and 3 credit tiers.
- POST/fiverr/v1/search
- POST/fiverr/v1/category
- POST/fiverr/v1/gig
- POST/fiverr/v1/seller
What Fiverr endpoints does ReefAPI ship?
4 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Fiverr API
3 of 4 endpoints, ready to run
Live gigs by keyword: title, starting price, delivery days, package count, rating and review count, with the paid placements excluded by default.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Fiverr API works
Fiverr is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 185 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Price a service category without pretending you can index it
The honest use of this engine is a sample, not a census — and the measurement below is why. A hundred-odd gigs off the front of a query is a real price distribution; a claim to have crawled two hundred thousand is not.
{"query": "logo design", "limit": 96}96 rows, each with a starting price, currency, delivery days, package count, rating and review count. Promoted placements are excluded unless you ask for them, and the meta echoes promoted_included so you can prove it.
{"id": "<row.url>"}Returns every package tier — three tiers on the gig we opened, at 1,400, 1,900 and 2,450 dollars, with 336, 504 and 720 delivery hours and 3, 6 and 8 revisions.
A defensible price curve for a category, with the tier structure behind each headline price — from a sample whose size you can state exactly.
curl -X POST https://api.reefapi.com/fiverr/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"logo design","limit":10}'{
"ok": true,
"data": { … },
"meta": {
"api": "fiverr",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}Seller level, package fields, and the same value in three different shapes
The three actions here read from three different Fiverr surfaces, so the same seller comes back with the same meaning in a different type depending on which one you called. If you are merging results, this table is the part that will bite you. Everything was read live on 2026-08-27 from search, gig and seller for the same seller and gig.
| Field | search returns | gig returns | seller returns |
|---|---|---|---|
| seller.level | "level_two_seller". Other values seen: "", "level_one_seller", "top_rated_seller" | 2 (an integer) | "LEVEL_TWO" |
| seller.id | 78762386 (a number) | "78762386" (a string) | "78762386" (a string) |
| languages[] | {code: "en", level: 3} | {code: "EN", level: "FLUENT"} | {code: "EN", level: "FLUENT"} |
| seller rating | 4.7543674, full precision | Not returned on the seller block | 4.9, rounded to one decimal |
| starting price | price.from 20 with currency USD | packages[0].price 20.0 with currency USD | price.from 20 on each gigs[] row |
| delivery | delivery_days 5, which is the Basic package | delivery_hours 120, 72 and 48 across the three packages | delivery_days null on gigs[] rows |
| revisions | Not returned | 5 on Basic, then -1 on both paid tiers | Not returned |
Basic, Standard and Premium are packages[].id 1, 2 and 3. The titles are whatever the seller typed, "Starter Pack -", "Pro Pack -" and "Elite Pack -" on the gig measured, so match on id and never on the title. revisions -1 means unlimited, not an error. Every review on the gig action came back with rating null, so take the score from reviews_summary.average; the reviews instead carry order_price_range as a band ("Up to $50", "$50-$100", "$100-$200"), order_duration_days and buyer_country. Paid promoted gigs are dropped by default, since Fiverr repeats the same ads at the top of every page; set include_promoted true to keep them, flagged is_promoted.
The reported count, the real ceiling, and the gap between them
Measured on 2026-08-28 by walking one query offset by offset until it stopped. The first line is the one that matters.
The listings are public and no login is involved, so there is no Fiverr account of yours in the path and nothing that can be limited or suspended. Failed calls are not charged.
Against us, and the single most important thing on this page. Searching one popular term reported between 175,556 and 193,895 gigs — the number changed across four calls in the same afternoon, which is what tells you it is an estimate rather than a count. Paging tells a very different story: offset 0 with limit 96 returned 96 rows, offset 96 returned 14 more, and offsets 192, 288, 384 and 456 each returned zero rows with stop_reason page_cap. About 110 gigs are reachable per query, against a claimed 190,000. Treat every query as a sample of roughly a hundred, and get breadth by running more queries and more categories rather than by paging deeper.
When it ends, the meta says stop_reason page_cap and returned 0 rather than repeating the first page or trailing off. You will always know you have hit the ceiling rather than the end of the market.
Fiverr injects the same promoted gigs at the top of every results page, which quietly corrupts any price distribution built from the raw pages. include_promoted defaults to false and every response echoes promoted_included, so the exclusion is verifiable rather than assumed.
Unlike every jobs engine in this batch, a gig is a standing offer rather than a dated posting, so there is no posted date to return. The time fields that do exist are the ones that matter commercially: delivery_days on the row, and delivery_hours per package on the detail.
The row's price block is the entry point — from, currency, delivery_days and package_count — and the real ladder is on the gig detail: each package with its own title, description, price, delivery hours and revision count. A category browse reported 237,517 gigs behind it, subject to the same paging ceiling as search.
Against us. The gig detail returns a reviews array and a reviews_summary, but on the gig we opened the individual reviews carried a null rating and a null order price. The summary average and total were correct; the per-review numbers were not there. Use the summary, not the rows.
The offer and its terms: title, category, packages, prices, delivery times, revisions, rating and review counts, and the seller's public trading attributes such as country and level. Reviews carry the buyer's country and nothing else. There is also a seller action, and it returns exactly what Fiverr itself publishes on a shop page — handle, display name, headline, country, timezone, languages, skills, hourly rate, level, rating, response time, join date. We opened one and it contained no e-mail address and no phone number, because the platform does not publish those. This page is deliberately not built around that action: the product here is the offer and its price, and the response sample published on this page has the seller block stripped out of it. The one place a shop handle does appear on this page is the pre-filled gig example above, because a Fiverr gig URL is built out of the handle and there is no other way to address a gig.
What people build with Fiverr
The jobs this data is most often used for.
endpoints
credits per call
Rate-benchmarking tools call search to chart starting price and delivery time across a service category.
Talent-sourcing platforms use seller to pull a freelancer's public level, country, rating and review count.
Marketplace researchers use category to measure supply and the price distribution inside one Fiverr category.
Competitive-intel tools use gig to compare a listing's package tiers and delivery times against their own.
What Fiverr data costs
The cheapest call here is 2 credits, so $15/mo (Pro) buys 5,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 185 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/fiverr/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"logo design","limit":10}'import requests
r = requests.post(
"https://api.reefapi.com/fiverr/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "logo design",
"limit": 10
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Fiverr.
Get a free key →What are the Fiverr seller level values?▾
Four, and one of them is an empty string. Across 48 gigs pulled for "python developer" on 2026-08-27, search returned level_two_seller on 30 sellers, level_one_seller on 7, top_rated_seller on 4, and "" on 7. The empty string is a seller who has not earned a level yet, not missing data, so do not treat it as null. Be aware that the same level arrives as the integer 2 on the gig action and as "LEVEL_TWO" on the seller action.
Does the API expose the Basic, Standard and Premium tiers?▾
Yes, on the gig action, as packages[]. A live read of one logo gig returned three packages with id 1, 2 and 3, price 20.0, 45.0 and 75.0 USD, delivery_hours 120, 72 and 48, and revisions 5, -1 and -1. Note the shape: id is the tier slot, the title is free text the seller wrote, and price rises as delivery_hours falls. search only shows you the cheapest tier, as price.from.
What does revisions -1 mean?▾
Unlimited revisions. It is Fiverr's sentinel for the "Unlimited" option in the package editor, and it appeared on both paid tiers of the measured gig while the Basic tier carried a real 5. Guard for it before you display or sort on the field, because a naive numeric sort will put the most generous packages last.
Is delivery time in days or hours?▾
Both, depending on the action. A search row gives price.delivery_days, an integer, which is the Basic package rounded up: 5 days for a gig whose Basic package is 120 hours. The gig action gives packages[].delivery_hours per tier, 120, 72 and 48 on the same gig. Hours are the precise figure. On the seller action's embedded gigs[] rows, delivery_days came back null altogether.
Why is the rating null on every review the gig action returns?▾
Fiverr does not publish a per-review star score on the gig page, only the text. All five reviews on the measured gig came back with rating null. The aggregate is right next to them: reviews_summary returned average 4.8 with total 2093 and has_more true. What the reviews do carry instead is unusual and useful, an order_price_range band such as "$100-$200", order_duration_days, and buyer_country.
Can I fetch a gig from its numeric id?▾
No. The gig action returns id 286340835 but will not accept it, because a Fiverr gig URL is /<seller-username>/<gig-slug> and the numeric id appears nowhere in the path. Pass either the full URL or "<seller>/<slug>". Both are on every search row as url and as slug plus seller.username, so carry one of them through your pipeline rather than the id.
How deep can I page through search results?▾
About 576 gigs per query. limit accepts 1 to 96 and offset accepts 0 to 480, so the deepest reachable row is 576, while a live search for "python developer" reported total_count 3677. Fiverr serves 48 per page, so asking for more than 48 walks extra pages for you. If you need the whole market, split the query by category or by keyword rather than trying to page past the offset ceiling.
What does the seller action add over the seller block on a search row?▾
The business profile. A live seller read added headline, country "Pakistan" with country_code PK, timezone "Asia/Karachi", joined_at as Unix epoch seconds (1563936663), response_time_hours 1, is_highly_responsive, is_agency, is_verified, is_on_vacation, hourly_rate with its currency (both null for this seller), reviews_count 3778 across all their work, and skills[] shaped {name, level, verified} with level "PRO". It also returns gigs[], every gig they list, each in the same shape as a search row.
What is the Fiverr API?▾
Fiverr API is a ReefAPI endpoint group for freelance gigs with starting prices, packages, delivery times and seller profiles. It returns live JSON through POST requests under /fiverr/v1.
Is the Fiverr API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Fiverr calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Fiverr login or account?▾
No login to Fiverr is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Fiverr data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Fiverr API use?▾
Fiverr actions currently cost 2-3 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Fiverr from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call fiverr actions with the same key, credit pool and JSON envelope used by normal REST requests.
15 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Fiverr, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 184 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-08-28.