> ## Documentation Index > Fetch the complete documentation index at: https://developers.marko.fr/llms.txt > Use this file to discover all available pages before exploring further. # Lire la chronologie narrative d'une opération > Agrège notamment les notes de suivi. Pour une note importée, metadata expose note_date, note_text et note_category. **Scope requis :** `operations:read`. [Scopes et délégation](/scopes-and-delegation). ## OpenAPI ````yaml /openapi.json get /operations/{operation_id}/chronicle/narrative openapi: 3.1.0 info: title: MARKO External Partner API version: v1 description: >- Stable external API contract for the live environment. Authentication flow for partner integrations: 1. Generate an API key from the MARKO entity admin API section. 2. Keep the raw API secret server-side and use it only to sign `POST /v1/auth/token`. 3. Build the canonical message `MARKO-EXTERNAL-API-TOKEN-V1\n{key_id}\n{timestamp}\n{nonce}`. 4. Sign that message with HMAC-SHA256 and send the hex signature with `key_id`, `timestamp` and `nonce`. 5. Use the returned short-lived bearer on business endpoints as `Authorization: Bearer `. The raw API secret must never be sent on business endpoints. This public contract intentionally excludes beta endpoints. Référence enrichie pour les développeurs et les assistants IA. Exemples synthétiques; les champs sont extraits des modèles et sérialiseurs de la version indiquée dans x-documentation-provenance. servers: - url: https://partner-api.marko.fr/v1 security: - BearerAuth: [] tags: - name: auth x-group: Authentification - name: entity x-group: Entité - name: portfolio x-group: Portefeuille - name: deals x-group: Deals - name: fonds x-group: Fonds - name: spvs x-group: SPV - name: operations x-group: Opérations - name: taxonomies x-group: Taxonomies - name: import-jobs x-group: Imports par lot - name: comments x-group: Commentaires - name: documents x-group: Documents - name: users x-group: Utilisateurs - name: settings x-group: Paramètres - name: rcci x-group: Conformité RCCI - name: field-definitions x-group: Champs métier - name: search x-group: Recherche - name: operateurs x-group: Opérateurs - name: alerts x-group: Alertes - name: notifications x-group: Notifications - name: calendar x-group: Calendrier - name: enrichment x-group: Enrichissement SIREN - name: reports x-group: Exports - name: reporting x-group: Templates de reporting - name: workflows x-group: Workflows et extraction IA - name: tasks x-group: Tâches externalDocs: description: Download the matching Postman collection. url: /v1/postman.json paths: /operations/{operation_id}/chronicle/narrative: get: tags: - operations summary: Lire la chronologie narrative d'une opération description: >- Agrège notamment les notes de suivi. Pour une note importée, metadata expose note_date, note_text et note_category. **Scope requis :** `operations:read`. [Scopes et délégation](/scopes-and-delegation). operationId: operations_chronicle_narrative parameters: - in: path name: operation_id required: true schema: type: string format: uuid title: Operation Id example: 44444444-4444-4444-4444-444444444444 description: UUID MARKO de l'opération. - in: query name: category required: false schema: anyOf: - $ref: '#/components/schemas/OperationChronicleCategory' - type: 'null' example: comment description: >- Catégorie de la note; les règles exactes dépendent de la route. Pour l'import externe: chaîne de 1 à 80 caractères, libre par défaut. - in: query name: page required: false schema: type: integer minimum: 1 default: 1 title: Page example: 1 description: >- Numéro de page; consultez la valeur minimale et la valeur par défaut de cette route. - in: query name: limit required: false schema: type: integer maximum: 200 minimum: 1 default: 50 title: Limit example: 50 description: >- Nombre maximal de résultats sur cette page; bornes et valeur par défaut ci-dessous. - in: header name: X-Request-ID required: false description: >- Partner-generated correlation identifier echoed in logs and error payloads. schema: type: string example: marko-operations-chronicle-narrative - name: date_from in: query required: false schema: anyOf: - type: string format: date-time - type: 'null' title: Date From description: Paramètre date_from de cette route; contraintes ci-dessous. - name: date_to in: query required: false schema: anyOf: - type: string format: date-time - type: 'null' title: Date To description: Paramètre date_to de cette route; contraintes ci-dessous. responses: '200': description: Successful response content: application/json: schema: $ref: '#/components/schemas/OperationChronicle' example: operation_id: 44444444-4444-4444-4444-444444444444 entries: - id: cm_aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa timestamp: '2026-07-15T09:30:00Z' category: comment title: Note d'appel ajoutée via l'API externe description: Pièces complémentaires attendues. severity: info metadata: note_date: '2026-07-15T09:30:00Z' note_text: Pièces complémentaires attendues. note_category: call total: 1 page: 1 pages: 1 limit: 50 sources_queried: - comments '401': description: Authentication required content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: about:blank title: Unauthorized status: 401 detail: A valid bearer token is required. request_id: req_example_partner_call '403': description: Scope, route or IP restriction content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: about:blank title: Forbidden status: 403 detail: The API key does not allow this operation. request_id: req_example_partner_call '422': description: Validation failed content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: about:blank title: Unprocessable Content status: 422 detail: The request payload or parameters are invalid. request_id: req_example_partner_call '429': description: Rate limit or progressive ban headers: Retry-After: description: Cooldown in seconds before retrying the request. schema: type: string content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: about:blank title: Too Many Requests status: 429 detail: The request rate limit was exceeded. request_id: req_example_partner_call '500': description: Unexpected server error content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: about:blank title: Internal Server Error status: 500 detail: An unexpected server error occurred. request_id: req_example_partner_call deprecated: false security: - BearerAuth: [] components: schemas: OperationChronicleCategory: type: string enum: - comment - alert - document - status - reporting title: OperationChronicleCategory description: Category of an operation chronicle narrative entry. OperationChronicle: properties: operation_id: type: string title: Operation Id description: UUID MARKO de l'opération. entries: items: $ref: '#/components/schemas/OperationChronicleEntry' type: array title: Entries description: Événements de la chronologie de l'opération. total: type: integer title: Total description: Nombre total de résultats correspondant aux filtres. page: type: integer title: Page description: Numéro de la page courante, à partir de 1. default: 1 pages: type: integer title: Pages description: Total pages default: 0 limit: type: integer title: Limit description: Items per page default: 50 sources_queried: items: type: string type: array title: Sources Queried description: Data sources included (comment, alert, document, status, reporting) type: object required: - operation_id - entries - total title: OperationChronicle description: >- Complete narrative chronicle for an operation. Aggregates events from multiple sources into a unified, chronologically-sorted timeline with narrative text. ProblemDetails: type: object required: - title - status - detail properties: type: type: string default: about:blank description: >- URI identifiant le type de problème; about:blank lorsque seul le statut HTTP le caractérise. title: type: string description: Titre affiché pour l'événement ou le problème. status: type: integer description: Statut HTTP de la réponse d'erreur. detail: type: string description: Informations détaillées sur le problème ou le dossier. request_id: type: string description: Identifiant de corrélation pour le diagnostic de la requête. scope: type: string description: Scope concerné par le refus d'accès, lorsqu'il est renseigné. route_id: type: string description: Identifiant de la route concernée par le problème. reason_code: type: string description: >- Code structuré du motif de refus; préférable au texte du message pour le diagnostic. OperationChronicleEntry: properties: id: type: string title: Id description: 'Prefixed ID: ''cm_{uuid}'', ''nt_{uuid}'', etc.' timestamp: type: string format: date-time title: Timestamp description: Heure Unix en secondes de l'échange signé. category: $ref: '#/components/schemas/OperationChronicleCategory' description: >- Catégorie de la note; les règles exactes dépendent de la route. Pour l'import externe: chaîne de 1 à 80 caractères, libre par défaut. title: type: string title: Title description: Short, action-oriented title description: anyOf: - type: string - type: 'null' title: Description description: 1-2 sentence narrative description severity: $ref: '#/components/schemas/OperationChronicleSeverity' default: info description: >- Niveau de gravité de l'événement, distinct de son statut de traitement. source_url: anyOf: - type: string - type: 'null' title: Source Url description: Deep-link to the source entity actor_id: anyOf: - type: string - type: 'null' title: Actor Id description: Identifiant de l'auteur de l'événement. actor_name: anyOf: - type: string - type: 'null' title: Actor Name description: Nom de l'auteur affiché dans la chronologie. metadata: anyOf: - additionalProperties: true type: object description: >- Objet JSON extensible. Les types des valeurs sont indiqués par additionalProperties lorsque la route les contraint. - type: 'null' title: Metadata description: >- Informations complémentaires de l'événement; leurs clés dépendent de son type. type: object required: - id - timestamp - category - title title: OperationChronicleEntry description: |- Single entry in the operation chronicle narrative timeline. Richer than ChronicleEntry: includes category, severity, source_url, and narrative-style title/description. OperationChronicleSeverity: type: string enum: - info - warning - critical title: OperationChronicleSeverity description: Severity level for a chronicle entry. securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: MARKO short-lived bearer description: >- Use the `access_token` returned by `POST /v1/auth/token`. Do not send the raw API secret on business endpoints. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.