hyreflow-ai

hyreflow-ai Playbook Leads API

The Playbook Leads API from hyreflow-ai — 2 operation(s) for playbook leads.

GitHub OpenAPI

Operations 2

POST /api/v2/playbook-leads Playbook Lead Create #
POST /api/v2/playbook-leads/{lead_id}/unlocks Playbook Lead Unlock #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/hyreflow-ai/openapi/hyreflow-ai-playbook-leads-api-openapi.yml

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/hyreflow-ai:hyreflow-ai-playbook-leads-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

hyreflow-ai-playbook-leads-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: hyreflow engine (local) Playbook Leads API
  version: 0.1.0
tags:
- name: Playbook Leads
paths:
  /api/v2/playbook-leads:
    post:
      summary: Playbook Lead Create
      description: 'Store a playbook lead (name + email + the playbook and utm it arrived with) and email them the

        reader link. The lead id IS the access credential, so it goes only into that email, never into this

        reply. A known email keeps its first touch (engine/playbook_leads.py) and is sent the same link

        again, so the form doubles as "get back in".'
      operationId: playbook_lead_create_api_v2_playbook_leads_post
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              type: object
              title: Body
              default: {}
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Playbook Leads
  /api/v2/playbook-leads/{lead_id}/unlocks:
    post:
      summary: Playbook Lead Unlock
      description: 'The reader''s access check: 204 (and one visit counted) when the emailed id names a lead, 410

        when it doesn''t (deleted on request, or never issued). The reader fails closed on anything else.

        `"playbook": null` (the library page) checks the lead and counts no visit.'
      operationId: playbook_lead_unlock_api_v2_playbook_leads__lead_id__unlocks_post
      parameters:
      - name: lead_id
        in: path
        required: true
        schema:
          type: string
          title: Lead Id
      requestBody:
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
              default: {}
              title: Body
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Playbook Leads
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer