Commit a2fbf543 authored by Alex Kakiris's avatar Alex Kakiris
Browse files

document GET /api/me/providers

parent 9250ccb4

README.md

+2 −1
Changes for README.md: 2 added lines, 1 removed line.
Original line number Diff line number Diff line
@@ -118,6 +118,7 @@ Endpoints acting on behalf of the logged-in user. They require a valid access to 
- POST /api/me/provider

  - Registers an API provider in CAPIF for the logged-in user, with one key pair and certificate per function (AEF, APF, AMF), all stored in a single Vault secret under `secret/backoffice/users/{uuid}/providers/{apiProvDomId}`.

  - Body: `{"apiProvDomInfo": "..."}`. Returns `201` `{"apiProvDomId": "..."}`.

- GET /api/me/providers: lists the logged-in user's apiProvDomIds (empty list if none).

- POST /api/me/providers/{apiProvDomId}/apis

  - Publishes an API in CAPIF as the provider's APF (mTLS with the APF certificate). The AEF is recorded as the function exposing the API.

  - Body: `apiName`, `apiVersion`, `resourceName`, `uri`, `operations`, `address`, `port` (required); `description`, `resourceDescription`, `protocol` (`HTTP_1_1`), `dataFormat` (`JSON`), `securityMethods` (`["OAUTH"]`) (optional). Returns `201` `{"apiId": "..."}`.
@@ -193,7 +194,7 @@ Implemented: 
- Authentication with access and refresh JWT tokens.

- Resource management for Invokers, Providers, APIs, and Users.

- Configuration and Register configuration management endpoints.

- User-scoped invoker onboarding (`POST /api/me/invoker`), with credentials stored in Vault.

- User-scoped CAPIF flow under `/api/me`: invoker onboarding, list and discover; provider onboarding, list and publish.



In progress:

- local_build.sh version automation and registry push flow.