So we have to include it separately. It's a little more text.

See https://github.com/OAI/OpenAPI-Specification/issues/417

Remove encryptedData and encryptedMetadata from the response when submitting a submission

Closes #95

See merge request fit-connect/api!109

Update status codes

Closes #98

See merge request fit-connect/api!108

feat(api#95): Remove encryptedData and encryptedMetadata from the response when submitting a submission

Add caseId for /submissions/ reponse bodies

Closes #100

See merge request fit-connect/api!106

Adapt the schema URL and name for the api spec

Closes docs#67

See merge request fit-connect/api!105

fix: Add /.well-known/jwks.json to API

See merge request fit-connect/api!100

refactor(submission): Refactor announcedContentStructure to announcedAttachments

See merge request fit-connect/api!99

Closes #92

Closes #81

feat(FCON-155): POST must have no <uuid> in path

See merge request fit-connect/api!97

Einheitliche Verwendung von LeiKa-Schlüssel vs. LeiKa-ID

See merge request fit-connect/api!94

Marco Holz authored 3 years ago and Jonas Gröger committed 3 years ago

Die mit '99' beginnende Zahlenfolge, die eine Leistung im LeiKa
eindeutig referenziert, wird als LeiKa-Schlüssel bezeichnet.
Zusätzlich gibt es zu jeder Leistung eine LeiKa-intern verwendete
LeiKa-ID.

Die Bezeichnungen wurden in der API entsprechend auf LeiKa-Schlüssel
vereinheitlicht.

FCON-155: Make .../keys endpoint POST (new key!)

See merge request fit-connect/api!96

feat(FCON-155): Add PatchDestination class to Schemas

See merge request fit-connect/api!95

api: typos

See merge request fit-connect/api!93