Jobo for .NET SDK
Live job data in C#.
Jobo.Enterprise.Client is the official .NET client for the Jobo API. It targets net6.0 and net8.0, exposes search, the bulk feed, expired job IDs, company profiles and geocoding as async sub-clients, and returns feeds as IAsyncEnumerable so an await foreach walks the whole cursor. A one-line extension registers it with dependency injection.
using Jobo.Enterprise.Client;
using Jobo.Enterprise.Client.Models;
using var client = new JoboClient(new JoboClientOptions
{
ApiKey = Environment.GetEnvironmentVariable("JOBO_API_KEY")!,
});
var results = await client.Search.SearchAsync(q: "software engineer", pageSize: 10);What can you do with the .NET SDK integration?
The official .NET client: async methods, IAsyncEnumerable feeds, and dependency-injection registration.
Async throughout
Every call is a Task-returning method, and enumeration methods return IAsyncEnumerable<Job>.
Dependency injection
services.AddJoboClient(o => o.ApiKey = ...) registers a singleton client for the rest of the application.
Typed exceptions
Failures throw JoboException subclasses carrying Code, StatusCode, Detail and the response body. JoboRateLimitException adds RetryAfterSeconds.
Same surface as Python and Node
All three official clients are on 4.0.0 and cover the same endpoints, so examples translate directly.
How do you connect .NET SDK to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Add the package
The client is published on NuGet as Jobo.Enterprise.Client.
bashdotnet add package Jobo.Enterprise.Client - 2
Create a client
JoboClient is IDisposable. Options also take BaseUrl, Timeout (30 seconds by default) and FeedTimeout (120 seconds by default).
csharpusing var client = new JoboClient(new JoboClientOptions { ApiKey = Environment.GetEnvironmentVariable("JOBO_API_KEY")!, }); - 3
Search
Filters are named arguments.
csharpvar results = await client.Search.SearchAsync(q: "software engineer", pageSize: 10); - 4
Stream the feed
For volume, enumerate the feed. The client follows the cursor for you.
csharpvar request = new JobFeedRequest { Sources = new List<string> { "greenhouse" }, BatchSize = 1000 }; await foreach (var job in client.Feed.EnumerateJobsAsync(request)) { await SaveToDatabaseAsync(job); }
What goes wrong with .NET SDK, and how do you fix it?
The things people actually hit when running Jobo in .NET SDK.
- Requests fail after passing your own HttpClient
- A supplied HttpClient is used as is. Set BaseAddress to https://connect.jobo.world, add the X-Api-Key default header, and give it a Timeout of at least 120 seconds if you use the feed.
- A filter the API documents is missing from the client
- The 4.0.0 clients do not cover every parameter. The client library docs list what is not covered; send those requests over plain HTTPS.
- Enum values stopped matching after upgrading
- 4.0.0 changed the EmploymentType, ExperienceLevel and CompensationPeriod value sets. Read the 4.0.0 upgrade notes before moving from 3.x.
How do you get the most out of .NET SDK?
- Register the client once with AddJoboClient rather than constructing it per request.
- Use EnumerateExpiredJobIdsAsync on a schedule to drop closed jobs from your copy. It is free.
- Pin the version exactly. 4.0.0 was a breaking release.
Which other Jobo integrations work alongside .NET SDK?
Start pulling live jobs into .NET SDK
One API key covers every integration, and the same job index sits behind all of them.













