Quartz.HttpClient
4.6.0
Prefix Reserved
dotnet add package Quartz.HttpClient --version 4.6.0
NuGet\Install-Package Quartz.HttpClient -Version 4.6.0
<PackageReference Include="Quartz.HttpClient" Version="4.6.0" />
<PackageVersion Include="Quartz.HttpClient" Version="4.6.0" />
<PackageReference Include="Quartz.HttpClient" />
paket add Quartz.HttpClient --version 4.6.0
#r "nuget: Quartz.HttpClient, 4.6.0"
#:package Quartz.HttpClient@4.6.0
#addin nuget:?package=Quartz.HttpClient&version=4.6.0
#tool nuget:?package=Quartz.HttpClient&version=4.6.0
Quartz.HttpClient
Quartz.HttpClient is the client half of the Quartz
HTTP API.
HttpScheduler is a full IScheduler implementation whose calls go over the wire, so an operator
process, a control panel or a deployment script schedules jobs against a remote scheduler with the same
code it would use against a local one.
Installation
dotnet add package Quartz.HttpClient
The server has to be running the HTTP API, which ships in Quartz.AspNetCore.
Usage
builder.Services.AddHttpClient("quartz", client =>
client.BaseAddress = new Uri("https://scheduler.example.com/quartz-api/"));
builder.Services.AddQuartzHttpClient(schedulerName: "MyScheduler", httpClientName: "quartz");
IScheduler is then injectable like any local one — keyed by scheduler name, and unkeyed while it is
the only scheduler in the container. new HttpScheduler(name, httpClient) does the same without a
container.
Two things must line up: the base address plus the API path have to reach the endpoints, and the name
the client is registered with has to be the remote scheduler's own SchedulerName — a mismatch is a
404, not a connection error. The base address must end in /.
Context and ListenerManager throw NotSupportedException: both are live in-process objects of the
scheduler, and listeners run where the jobs run. The remaining property members of IScheduler
(Status, SchedulerInstanceId) each block the calling thread for a round trip, so use
GetMetadata() on a request path.
Documentation
https://www.quartz-scheduler.net/documentation/quartz-4.x/packages/http-client.html
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.Configuration.Binder (>= 10.0.0)
- Microsoft.Extensions.DependencyInjection (>= 10.0.0)
- Microsoft.Extensions.Diagnostics.HealthChecks (>= 10.0.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.0)
- Microsoft.Extensions.Http (>= 10.0.0)
- Microsoft.Extensions.Logging (>= 10.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.0)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.0)
- Quartz (>= 4.6.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Quartz.HttpClient:
| Package | Downloads |
|---|---|
|
Quartz.Dashboard
Quartz.NET Blazor Server Dashboard - a live view of every scheduler in the application, its jobs, triggers and calendars; Quartz Scheduling Framework for .NET |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.6.0 | 937 | 10/19/2026 |
| 4.5.1 | 1,187 | 10/15/2026 |
| 4.5.0 | 836 | 10/13/2026 |
| 4.4.0 | 98 | 10/7/2026 |
| 4.3.0 | 143 | 9/29/2026 |
| 4.2.4 | 100 | 9/29/2026 |
| 4.2.3 | 113 | 9/28/2026 |
| 4.2.2 | 105 | 9/28/2026 |
| 4.2.1 | 102 | 9/27/2026 |
| 4.2.0 | 115 | 9/25/2026 |
| 4.1.1 | 127 | 9/19/2026 |
| 4.1.0 | 113 | 9/13/2026 |
| 4.0.1 | 163 | 9/8/2026 |
| 4.0.0 | 126 | 9/3/2026 |
| 4.0.0-rc.2 | 79 | 9/3/2026 |
| 4.0.0-rc.1 | 89 | 9/3/2026 |
| 4.0.0-beta.1 | 86 | 9/2/2026 |
| 4.0.0-alpha.5 | 78 | 8/31/2026 |
| 4.0.0-alpha.4 | 81 | 8/31/2026 |
| 4.0.0-alpha.3 | 85 | 8/27/2026 |