Marketplace APIs¶
Why This Exists¶
This document defines API responsibilities for the Marketplace Domain.
It does not define implementation code or final OpenAPI specifications.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Marketplace APIs expose governed listing, category, search, visibility, matching, recommendation display, and request workflows.
API Groups¶
| API group | Responsibilities | Example endpoints |
|---|---|---|
| Marketplace Listing API | Create and manage listings. | POST /marketplace/listings, GET /marketplace/listings/{listingId} |
| Provider Category API | Manage categories. | GET /marketplace/categories, POST /marketplace/categories |
| Marketplace Search API | Search and browse providers. | GET /marketplace/search |
| Visibility API | Manage listing visibility. | PATCH /marketplace/listings/{listingId}/visibility |
| Verification Display API | Manage displayed verification signals. | GET /marketplace/listings/{listingId}/verification-display |
| Marketplace Matching API | Match customer needs to providers. | POST /marketplace/matches |
| Quote Request API | Manage quote request workflow. | POST /marketplace/quote-requests |
| Support Request API | Manage support request workflow. | POST /marketplace/support-requests |
| Recommendation Display API | Record displayed recommendations. | POST /marketplace/recommendation-displays |
API Principles¶
- APIs must not mutate Supplier, Funding, Organization, Contract, or Intelligence source facts.
- APIs may display external signals only with source references.
- APIs must preserve marketplace workflow state and request audit.
- APIs must publish marketplace events for meaningful changes.