> ## 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. # Lister le socle canonique MARKO historique > Endpoint legacy: retourne uniquement le socle canonique MARKO historique. Les écritures acceptent aussi les valeurs propres à l'entité. Utilisez `GET /v1/taxonomies?dimension=...` pour la liste visible et autoritative, y compris les options ClubFunding. **Scope requis :** `operations:read`. [Scopes et délégation](/scopes-and-delegation). ## OpenAPI ````yaml /openapi.json get /operations/taxonomy 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/taxonomy: get: tags: - operations summary: Lister le socle canonique MARKO historique description: >- Endpoint legacy: retourne uniquement le socle canonique MARKO historique. Les écritures acceptent aussi les valeurs propres à l'entité. Utilisez `GET /v1/taxonomies?dimension=...` pour la liste visible et autoritative, y compris les options ClubFunding. **Scope requis :** `operations:read`. [Scopes et délégation](/scopes-and-delegation). operationId: operations_taxonomy parameters: - 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-taxonomy responses: '200': description: Successful response content: application/json: schema: $ref: '#/components/schemas/ExternalOperationTaxonomyResponse' example: default_status: sourcing statuses: - code: sourcing label: Analyse initiale - code: instruction label: Instruction - code: travaux label: Travaux - code: commercialisation label: Commercialisation - code: livraison label: Livraison - code: cloture label: Clôture - code: perte label: Perdue statuts_internes: - code: due_diligence label: Due diligence - code: en_cours label: En cours - code: en_recouvrement label: En recouvrement - code: analyse label: Analyse - code: comite label: Comité - code: closing label: Closing - code: sain label: Sain - code: avenant label: Avenant - code: pre_contentieux label: Précontentieux - code: contentieux_judiciaire label: Contentieux judiciaire - code: lj label: LJ - code: rj_sauvegarde label: RJ ou sauvegarde - code: procedure_preventive label: Procédure préventive - code: protocole_transactionnel label: Protocole transactionnel - code: pre_contentieux_recouvrement label: Précontentieux - code: remboursement_partiel label: Sortie partielle - code: recouvrement_partiel label: Recouvrement partiel - code: termine label: Terminé statuts_operationnels: - code: montage_et_faisabilite label: Montage et faisabilité - code: offre_foncier label: Offre - Foncier - code: promesse_unilaterale_de_vente label: Promesse unilatérale de vente - code: acquisition_du_foncier label: Acquisition du foncier - code: evictions label: Évictions - code: depot_de_la_dp label: Dépôt de la DP - code: dp_purge label: DP purgé - code: depot_du_pc label: Dépôt du PC - code: pc_purge label: PC purgé - code: depot_du_pcm label: Dépôt du PCM - code: pcm_purge label: PCM purgé - code: gfa label: GFA - code: travaux label: Travaux - code: commercialisation label: Commercialisation - code: commercialisation_locative label: Commercialisation locative - code: achevement_dat label: Achèvement (DAT) - code: livraison label: Livraison / Cession d'actif - code: leve_des_reserves label: Levée des réserves - code: suivi_du_sav label: Suivi du SAV - code: decennale label: Décennale '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: true security: - BearerAuth: [] components: schemas: ExternalOperationTaxonomyResponse: properties: default_status: $ref: '#/components/schemas/OperationStatus' description: Statut canonique proposé par défaut pour une opération. statuses: items: $ref: '#/components/schemas/ExternalOperationTaxonomyOption' type: array title: Statuses description: >- Statuts du socle canonique historique; GET /taxonomies expose aussi les options visibles de l'entité. statuts_internes: items: $ref: '#/components/schemas/ExternalOperationTaxonomyOption' type: array title: Statuts Internes description: Statuts internes du socle canonique historique. statuts_operationnels: items: $ref: '#/components/schemas/ExternalOperationTaxonomyOption' type: array title: Statuts Operationnels description: Statuts opérationnels du socle canonique historique. type: object required: - default_status - statuses - statuts_internes - statuts_operationnels title: ExternalOperationTaxonomyResponse 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. OperationStatus: type: string enum: - sourcing - instruction - travaux - commercialisation - livraison - cloture - perte title: OperationStatus description: Statut métier de l'opération. ExternalOperationTaxonomyOption: properties: code: type: string title: Code description: >- Code stable de la ressource ou de l'option. Conserver la valeur retournée par MARKO. label: type: string title: Label description: Libellé à afficher pour cette option, ce groupe ou ce preset. type: object required: - code - label title: ExternalOperationTaxonomyOption 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.