IS Jobs REST API
https://isjobs.xyz/api/v1/jobsSearch and read published academic Information Systems jobs without authentication. Scoped bearer tokens enable submissions, corrections, and private tracker operations.
Loading IS Jobs…
IS Jobs developer resources
Use the public REST API for portable HTTP integrations, the OpenAPI contract for generated clients and tool discovery, or the MCP server when an AI assistant needs scoped actions and interactive authorization.
https://isjobs.xyz/api/v1/jobsSearch and read published academic Information Systems jobs without authentication. Scoped bearer tokens enable submissions, corrections, and private tracker operations.
https://isjobs.xyz/openapi.jsonThe machine-readable source of truth for REST paths, schemas, OAuth scopes, error envelopes, and response status codes.
https://isjobs.xyz/mcpA Streamable HTTP Model Context Protocol server for assistants that need job discovery, evidence-backed suggestions, submissions, or an authorized private tracker.
Published job reads require no account, API key, sales contact, or trial. Query the versioned endpoint directly, then follow each result’s canonical IS Jobs permalink or original employer URL. Public records are production data, so clients should treat them as read-only unless they intentionally call a documented write operation.
curl --get 'https://isjobs.xyz/api/v1/jobs' \
--data-urlencode 'q=information systems' \
--data-urlencode 'region=North America' \
--data-urlencode 'limit=10' \
-H 'Accept: application/json'Accounts are free and self-service. Sign in, open API access settings, and create a personal bearer token with only the scopes the integration needs. OAuth clients can use authorization code with PKCE, dynamic client registration, protected-resource metadata, refresh rotation, and revocation. MCP clients discover the same OAuth flow from the server metadata.
Use REST for deterministic list, record, and tracker calls. Use MCP when an assistant benefits from tool descriptions and an interactive consent screen. Choose jobs:suggest for evidence-backed corrections that require human review; it grants less authority than direct editing. IS Jobs does not currently offer a separate write sandbox, so integrations should use public reads while developing and avoid mutation tools until their production intent is clear.
REST failures use a JSON envelope with a stable machine code, a human-readable message, and a resolution hint. Validation failures may add field details, and unexpected failures add a request ID that can be shared without exposing server internals. Unknown /api paths also use this envelope instead of returning an HTML page.
{
"error": {
"code": "not_found",
"message": "Job not found.",
"resolution": "Check the request URL and use the API index or OpenAPI document to find a supported endpoint."
}
}Stable REST operations are versioned in the URL under /api/v1. Compatible additions, such as optional response fields or new endpoints, may ship within v1. A breaking request or response change will use a new major path so existing clients can continue calling v1.
If a stable version is deprecated, IS Jobs will publish a migration guide and keep the version available for at least six months. Affected responses will use the standardized Deprecation header and a rel="deprecation" link. When a shutdown date is known, they will also include a Sunset header. The OpenAPI description and this page will identify the replacement. No v1 REST operation is currently deprecated.