Fiverr seller API

Endpoint facts

Method

GET

API path

/fiverr/seller/{username}

Auth

apiKey

Credits

5 credits/request

Platform

Fiverr

Response schema

#/definitions/fiverr.sellerResponseDoc

Overview

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. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

5 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- `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", "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"] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related