TTauracoDocumentation
FREN
The Tauraco siteapp.tauraco.io
Home › Developer portal › Tauraco Collateral documentation
Document menu← Home
Developer portal
  1. Quick start
  2. Authentication
  3. REST API reference
  4. Webhooks guide
  5. Exports guide
  6. ERP integration guide
  7. Bank integration guide
  8. Tauraco Collateral documentation
  9. MCP documentation
  10. Code samples
  11. Error handling
  12. Sandbox environments
  13. Versions and changelog
  14. FAQ
  15. Developer support
Developers

Tauraco Collateral documentation

Tauraco Collateral tracks the OHADA security interests attached to financing: pledges of inventory held by a third-party custodian, charges, registry entries, releases, expiry alerts. The hub exposes it read-only, with a systematic legal notice.

Status on 2026-11-05: the collateral_depots dataset, the REST read, the collateral.* events, the MCP tools and the bank view are developed and tested; in production since 2026-11-05, with the matching modules (exports, public API, v2 webhooks, MCP, bank API).

What is exposed

SurfaceContentScope
REST read: GET /collateral/depots (paginated list) and GET /collateral/depots/{depot_id}same fields as the collateral_depots datasetcollateral:read, ERP_OWNER delegator only
Export, from the application or through POST /exports (company side)collateral_depots dataset: id, type_garantie, nature, pays, statut_metier, date_acte, date_peremption (optional), created_at, updated_at, avertissement_juridiquecollateral:read (and exports:write to request the export through the API)
MCP (company side)tauraco_list_collateral, tauraco_get_collateral_statusmcp:read and collateral:read
Bank API (institution side)security interests in favour of the institution: list with summarised alerts, detail without private notes, timeline; neither the asset registry nor the alert sheet in v1bank:collateral:read
Webhooks (institution side)collateral.registered, collateral.released (guarantee_id, partial, dates, legal_notice)collateral:read

No amount, no inventory value and no rate is served by these surfaces. Field names of the Collateral dataset are in French, as in the Collateral engine.

Every row carries a notice. For deposits held by a third-party custodian, the current French text reads: « Information de suivi : cette ligne constate la remise d'un stock gagé à un tiers détenteur. Elle ne vaut ni inscription au registre compétent, ni preuve de l'opposabilité ou du rang de la sûreté. » (Tracking information: this row records that pledged inventory was handed over to a third-party custodian. It is neither a registration with the competent registry nor proof that the security interest is enforceable or of its rank.)

This text was validated on 2026-11-05 (Sega's decision), before the bank API was opened. Do not use it as a legal qualification, and never present Tauraco data as proof of an enforceable security interest.

What is not exposed

  • No discharge, no release, no registration through the API or MCP: these actions are reserved to a human decision-maker, in the portal, after the beneficiary and authorisation checks.
  • No private file note (dossier_prive).
  • The guarantees:read scope (ecosystem bonds) is reserved: no resource in v1.

Read the deposits

curl -sS -X POST "https://api.tauraco.io/public/v1/exports" \
  -H "Authorization: Bearer ${TAURACO_TOKEN}" -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"datasets":[{"dataset":"collateral_depots"}],"format":"json"}'

The dataset is read over REST (GET /collateral/depots, ERP_OWNER delegator only), through an export (above, then GET /exports/{job_id}/download), from My exports or through the MCP tools. Every row carries avertissement_juridique.