Cape Partners

Cape Partners Data Quality API

The DataQuality API from Cape Partners — 1 operation(s) for dataquality.

Documentation GitHub OpenAPI

Business capability

Data Quality Management BC-610.30

Operations 1

POST /api/dq/enqueue Enqueue high-priority data-quality improvement steps for a seller or buyer for… #

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/capepartners-fr:capepartners-fr-dataquality-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.

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: Cape Partners — Sniffer Agent Data Quality API
  version: 1.0.0
  description: Machine-readable API backing the Cape Partners M&A deal-flow workspace (click, humans).
  contact:
    name: Cape Partners
    url: https://www.capepartners.fr
servers:
- url: https://www.capepartners.fr
  description: Production (www) via Cloudflare
- url: https://sniffer.capepartners.fr
  description: Workspace host
- url: http://localhost:3000
  description: Local dev
tags:
- name: DataQuality
paths:
  /api/dq/enqueue:
    security:
    - SessionToken: []
    post:
      summary: Enqueue high-priority data-quality improvement steps for a seller or buyer for…
      tags:
      - DataQuality
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DqEnqueueResponse'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DqEnqueueRequest'
      operationId: postApiDqEnqueue
      x-operation-id-source: derived
components:
  schemas:
    DqEnqueueResponse:
      type: object
      properties:
        ok:
          type: boolean
        enqueued:
          type: integer
        steps:
          type: array
          items:
            type: string
        entity_type:
          type: string
        entity_id:
          type: integer
    DqEnqueueRequest:
      type: object
      properties:
        entity_type:
          type: string
          enum:
          - seller
          - buyer
        entity_id:
          type: integer
        steps:
          type: array
          items:
            type: string
          description: 'Default seller steps: [siren, financials, president, advisor, contacts, product]; buyer: [discovery, profile]'
      required:
      - entity_type
      - entity_id
  securitySchemes:
    SessionToken:
      type: apiKey
      in: header
      name: X-Session-Id
      description: 'The workspace session UUID is a capability token carried in the URL PATH (not this header — shown here only because OpenAPI securitySchemes cannot model a path parameter as a credential). A valid request must present a well-formed UUID-v4 in the path segment {session_id} AND a first-party Origin/Referer (or none). Requests carrying a known-foreign Origin/Referer are refused 403. Per-IP rate limiting applies. All responses carry Referrer-Policy: strict-origin-when-cross-origin.'
    NdaSigned:
      type: apiKey
      in: header
      name: X-Nda-Signed
      description: 'Precondition (not a literal header): a server-side NDA signature for {session_id} must be recorded in the nda_signatures table via POST /api/nda/sign before NDA-gated resources (/api/matched-names, /api/infomemo/*) will serve data. Recorded signatures are enforced server-side (helper `nda_signed`), not by trusting a client header.'