hyreflow-ai

hyreflow-ai Support API

The Support API from hyreflow-ai — 1 operation(s) for support.

Documentation GitHub OpenAPI

Operations 1

POST /api/v2/support Support Request #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/hyreflow-ai/openapi/hyreflow-ai-support-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-support-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

openapi: 3.2.0
info:
  title: hyreflow engine (local) Support API
  version: 0.1.0
tags:
- name: Support
paths:
  /api/v2/support:
    post:
      summary: Support Request
      description: 'Public docs/dashboard feedback-widget submission. Auth is optional — docs visitors aren''t signed

        in, the dashboard is — and a signed-in `technical` report also unifies onto the `feedback` table

        (Support dashboard) and files an issue, same as the other two ingest paths. Always emails the

        support inbox first, unchanged; persist+file happen after and are best-effort, so a DB/Linear

        hiccup never turns an email that already sent into a 500 (and a resubmit — a duplicate email).'
      operationId: support_request_api_v2_support_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'
      security:
      - HTTPBearer: []
      tags:
      - Support
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