New to Gradio? Start here: Getting Started

Using Zero Gpu Spaces

Job

Client

gradio_client.Client(···)

Description

The main Client class for the Python client. This class is used to connect to a remote Gradio app and call its API endpoints.

Example usage

from gradio_client import Client

client = Client("abidlabs/whisper-large-v2")  # connecting to a Hugging Face Space
client.predict("test.mp4", api_name="/predict")
>> What a nice recording! # returns the result of the remote API call

client = Client("https://bec81a83-5b5c-471e.gradio.live")  # connecting to a temporary Gradio share URL
job = client.submit("hello", api_name="/predict")  # runs the prediction in a background thread
job.result()
>> 49 # returns the result of the remote API call (blocking call)

Initialization

🔗

src: str

either the name of the Hugging Face Space to load, (e.g. "abidlabs/whisper-large-v2") or the full URL (including "http" or "https") of the hosted Gradio app to load (e.g. "http://mydomain.com/app" or "https://bec81a83-5b5c-471e.gradio.live/").

🔗

hf_token: str | Literal[False] | None

default = False

optional Hugging Face token to use to access private Spaces. By default, no token is sent to the server. Set `hf_token=None` to use the locally saved token if there is one (warning: only provide a token if you are loading a trusted private Space as the token can be read by the Space you are loading). Find your tokens here: https://huggingface.co/settings/tokens.

🔗

max_workers: int

default = 40

maximum number of thread workers that can be used to make requests to the remote Gradio app simultaneously.

🔗

verbose: bool

default = True

whether the client should print statements to the console.

🔗

auth: tuple[str, str] | None

default = None

🔗

httpx_kwargs: dict[str, Any] | None

default = None

additional keyword arguments to pass to `httpx.Client`, `httpx.stream`, `httpx.get` and `httpx.post`. This can be used to set timeouts, proxies, http auth, etc.

🔗

headers: dict[str, str] | None

default = None

additional headers to send to the remote Gradio app on every request. By default only the HF authorization and user-agent headers are sent. This parameter will override the default headers if they have the same keys.

🔗

download_files: str | Path | Literal[False]

default = "/tmp/gradio"

directory where the client should download output files on the local machine from the remote API. By default, uses the value of the GRADIO_TEMP_DIR environment variable which, if not set by the user, is a temporary directory on your machine. If False, the client does not download files and returns a FileData dataclass object with the filepath on the remote machine instead.

🔗

ssl_verify: bool

default = True

if False, skips certificate validation which allows the client to connect to Gradio apps that are using self-signed certificates.

🔗

analytics_enabled: bool

default = True

Whether to allow basic telemetry. If None, will use GRADIO_ANALYTICS_ENABLED environment variable or default to True.

Event Listeners

Description

Event listeners allow you to respond to user interactions with the UI components you've defined in a Gradio Blocks app. When a user interacts with an element, such as changing a slider value or uploading an image, a function is called.

Supported Event Listeners

The Client component supports the following event listeners. Each event listener takes the same parameters, which are listed in the Event Parameters table below.

Listener	Description
`Client.predict(fn, ···)`	Calls the Gradio API and returns the result (this is a blocking call). Arguments can be provided as positional arguments or as keyword arguments (latter is recommended). <br>
`Client.submit(fn, ···)`	Creates and returns a Job object which calls the Gradio API in a background thread. The job can be used to retrieve the status and result of the remote API call. Arguments can be provided as positional arguments or as keyword arguments (latter is recommended). <br>
`Client.view_api(fn, ···)`	Prints the usage info for the API. If the Gradio app has multiple API endpoints, the usage info for each endpoint will be printed separately. If return_format="dict" the info is returned in dictionary format, as shown in the example below. <br>
`Client.duplicate(fn, ···)`	Duplicates a Hugging Face Space under your account and returns a Client object for the new Space. No duplication is created if the Space already exists in your account (to override this, provide a new name for the new Space using `to_id`). To use this method, you must provide an `hf_token` or be logged in via the Hugging Face Hub CLI. <br> The new Space will be private by default and use the same hardware as the original Space. This can be changed by using the `private` and `hardware` parameters. For hardware upgrades (beyond the basic CPU tier), you may be required to provide billing information on Hugging Face: https://huggingface.co/settings/billing <br>
`Client.deploy_discord(fn, ···)`	Deploy the upstream app as a discord bot. Currently only supports gr.ChatInterface.

Event Parameters

🔗

args: <class 'inspect._empty'>

The positional arguments to pass to the remote API endpoint. The order of the arguments must match the order of the inputs in the Gradio app.

🔗

api_name: str | None

default = None

The name of the API endpoint to call starting with a leading slash, e.g. "/predict". Does not need to be provided if the Gradio app has only one named API endpoint.

🔗

fn_index: int | None

default = None

As an alternative to api_name, this parameter takes the index of the API endpoint to call, e.g. 0. Both api_name and fn_index can be provided, but if they conflict, api_name will take precedence.

🔗

kwargs: <class 'inspect._empty'>

The keyword arguments to pass to the remote API endpoint.

←

Using Zero Gpu Spaces

Job

→