How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cape Partners Pairings API

The Pairings API from Cape Partners — 4 operation(s) for pairings.

Cape Partners Pairings API is one of 16 APIs that Cape Partners publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pairings. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 4 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://www.capepartners.fr, https://sniffer.capepartners.fr, http://localhost:3000.

4 operations 4 paths 7 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://sniffer.capepartners.fr
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Cape Partners Pairings API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Session-Id (SessionToken). An API key is passed in the header as X-Nda-Signed (NdaSigned).

  • SessionToken — 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…
  • NdaSigned — Precondition (not a literal header): a server-side NDA signature for {sessionid} must be recorded in the ndasignatures table via POST /api/nda/sign before NDA-…

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Pairings 4
GET
/api/pairings/{session_id}
Return pairings for the session (as buyer or seller), with match score, phase…
getApiPairingsBySessionId 1 param → 200404403
POST
/api/pairings/create
Create a new pairing (pair-{buyerid}-{sellerid}) between a buyer and seller
postApiPairingsCreate body → 201409400
POST
/api/pairings/update_phase
Bulk-update deal phase for one or more pairings.
postApiPairingsUpdatePhase body → 200400
POST
/api/pairings/phase-request
Answer a pending phase-change request — the other half of the mutual-consent…
postApiPairingsPhaseRequest body → 200400403409404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Pairing (23 properties), PendingPhaseRequest (9 properties), PairingsResponse (7 properties), PhaseRequestDecisionResponse (6 properties). Each schema is shown below with its type and property counts.

PairingCreateResponse
object
5 properties
PairingsResponse
object
7 properties
PhaseUpdateResponse
object
5 properties
PairingCreateRequest
object
4 properties 2 required
PendingPhaseRequest
object
A live phase-change request on this pairing (mutual consent). While it exists the pairing is LOCKED: the phase stays visible but no phase change is accepted un…
9 properties
Pairing
object
23 properties
PhaseRequestDecisionResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

capepartners-fr-pairings-api-openapi.yml Raw ↑

Other APIs Cape Partners publishes across the network.

Cape Partners Agent Exchange (A2A)
Cape Partners Activity API
Cape Partners Confidentiality API
Cape Partners Data Quality API
Cape Partners Deal Flow API
Cape Partners Discovery API
Cape Partners Exchange API
Cape Partners Identity API
Cape Partners Info Memos API
Cape Partners Interest API
Cape Partners Mandate API
Cape Partners Matching API
Where this information came from

This is an independent, third-party profile of Cape Partners Pairings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.