Catalog

Fiverr API

Fiverr data through one normalized API - per-request USD pricing and no subscriptions.

Endpoints1Providers1From · search$1.65/1k results · OctopusFull breakdownRead docs
Uptime
97.30%
30d · 37 calls
Requests
37
30d · weekly, last 12 wks
Response
12.6s
median · 30d

Measured performance

What the Fiverr API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

97.3%
of calls succeeded (37 calls)
Succeeded on first lane 97.3%Failed 2.7%
Response time (36 calls)
Typical (p50)
12.6s
Half of requests finish within 12.6s
p99 response time
59.8s
p99 response time: 99% of requests finish within 59.8s

FAQ

About the Fiverr API

The AnyAPI Fiverr API returns Fiverr data as normalized JSON across 1 endpoint: search. You call one endpoint per job with a single key, and AnyAPI returns one normalized schema whichever source serves it. Pricing is in US dollars, $1.65 per 1,000 results, and never more than $0.033 for a single request, with no subscription and no monthly minimum. Over the last 30 days, 97.3% of Fiverr calls through AnyAPI succeeded, with a median response time of 12.6 seconds across 37 measured calls.

Pricing is in US dollars, $1.65 per 1,000 results, and never more than $0.033 for a single request, with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

One endpoint: search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Fiverr endpoint is a change of URL and nothing else.

Over the last 30 days, 97.3% of Fiverr calls through AnyAPI succeeded, with a median response time of 12.6 seconds across 37 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.