timzinin-com Job Alert API

The Job Alert API from timzinin-com — 1 operation(s) for job alert.

Operations 1

POST /api/job-alert New Job Alert #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-job-alert-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

timzinin-com-job-alert-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Zinin M2M Hub Job Alert API
  description: Pay-per-call data & tool APIs
  version: 1.0.0
  x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Job Alert
paths:
  /api/job-alert:
    post:
      summary: New Job Alert
      description: Watches a job board for a saved filter and returns only the postings that appeared since the previous check. The first run on a new filter creates the baseline and says so.
      operationId: call_job_alert
      x-payment-info:
        price:
          mode: fixed
          currency: USD
          amount: '0.050000'
        protocols:
        - x402: {}
        network: eip155:8453
        payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
        asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              title: New Job Alert input
              type: object
              schemaVersion: 1
              properties:
                board:
                  title: Board to watch
                  type: string
                  description: Which of our own live job-board Actors this watch calls. Each board's own filter fields differ — see the Input section of the README for the exact fields each one expects.
                  prefill: jobs-ch-swiss
                  default: jobs-ch-swiss
                  enum:
                  - jobs-ch-swiss
                  - xing-jobs
                  - boss-az
                  enumTitles:
                  - jobs.ch (Switzerland)
                  - XING Jobs (DACH)
                  - Boss.az (Azerbaijan)
                filter:
                  title: Board filter (JSON)
                  type: object
                  description: The search filter to pass to the chosen board's own Actor input — same field names as that Actor's own input schema (e.g. jobs.ch wants {"keywords":["marketing"]}, XING/Boss.az want {"keyword_filter":"marketing"}). See the README's Input table for every board's fields. Any "max_items"/"max_pages" you set here are capped at 10/2 regardless of the board's own limits, to keep each check fast and cheap.
                  editor: json
                  prefill:
                    keywords:
                    - marketing
                    max_items: 3
                    max_pages: 1
                baseline_key:
                  title: Watch name
                  type: string
                  description: A name for THIS watch, so you can run several independent watches (different boards and/or filters) from one Actor without one overwriting another's memory of what's already been seen. Each name is scoped to YOUR OWN Apify account. The prefilled value is only there so this Actor's own daily test run has a stable, obviously-a-test name; replace it with your own watch name.
                  editor: textfield
                  prefill: apify-daily-test
                max_items:
                  title: Max new postings per run
                  type: integer
                  description: Caps how many NEW-posting rows a single run will deliver and charge for, even if more were found.
                  default: 20
                  minimum: 1
                  maximum: 200
              required:
              - board
              - filter
      responses:
        '200':
          description: Actor run succeeded and payment settled
          content:
            application/json:
              schema:
                type: object
                properties:
                  results:
                    type: array
                    items:
                      type: object
                    description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
                  meta:
                    type: object
                    properties:
                      run_ms:
                        type: integer
                        description: Actor run duration in milliseconds
                      item_count:
                        type: integer
                        description: len(results)
                      settled:
                        type: boolean
                        description: Whether the x402 payment was confirmed settled by the facilitator
                      transaction:
                        type:
                        - string
                        - 'null'
                        description: On-chain settlement transaction hash, null if unsettled
                    required:
                    - run_ms
                    - item_count
                    - settled
                    - transaction
                required:
                - results
                - meta
        '400':
          description: Malformed PAYMENT-SIGNATURE header or request body
        '402':
          description: Payment required or invalid — see PAYMENT-REQUIRED header
        '409':
          description: Payment payload already used
        '502':
          description: Actor run failed
        '504':
          description: Actor run timed out
      tags:
      - Job Alert