timzinin-com Hiring Trend Index API

The Hiring Trend Index API from timzinin-com — 1 operation(s) for hiring trend index.

Operations 1

POST /api/hiring-trend-index Hiring Trend Index #

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-hiring-trend-index-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-hiring-trend-index-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Zinin M2M Hub Hiring Trend Index 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: Hiring Trend Index
paths:
  /api/hiring-trend-index:
    post:
      summary: Hiring Trend Index
      description: A cross-section of hiring demand by role and geography, assembled from several job sources in one call. Partial results are marked partial and list what is missing.
      operationId: call_hiring_trend_index
      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: Hiring Trend Index input
              type: object
              schemaVersion: 1
              properties:
                slices:
                  title: Slices to watch
                  type: array
                  description: 'What to snapshot and track. Two forms: "company:<ats-provider>:<token>" (e.g. "company:greenhouse:gitlab", "company:ashby:ramp") pulls a company''s own public job board via this Actor''s own live company-hiring-radar Actor. "board:<board-name>[:<keyword>]" (e.g. "board:xing-jobs", "board:jobs-ch-swiss:marketing") pulls a sample from one of this factory''s own job-board Actors — see README for which board names are live today. Every run re-checks the SAME slices and reports what changed (by job function) since the last check for each one.'
                  editor: stringList
                  prefill:
                  - company:greenhouse:gitlab
                  - company:greenhouse:stripe
                  maxItems: 10
                watch_key:
                  title: Watch name
                  type: string
                  description: A name for THIS set of watches, so you can run several independent hiring-trend watches from one Actor without one overwriting another's memory of what it last saw. 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.
                  editor: textfield
                  prefill: apify-daily-test
                new_window_days:
                  title: '"New posting" window (company slices only)'
                  type: integer
                  description: For company slices, how many days back a posting still counts as "new" in the underlying company-hiring-radar signal. Has no effect on board slices.
                  default: 30
                  minimum: 1
                  maximum: 365
              required:
              - slices
      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:
      - Hiring Trend Index