Organizations: assets, suppliers, and documents.

Last updated 8 Jul 20262 min read

Organizations are the anchor for tailored intelligence: what Liberty91 knows about an organization's assets, technologies, and suppliers shapes every report and relevance decision made for it. These endpoints let you read that context and keep it current from your own systems.

Reading requires orgs.read; uploads, confirmations, and description updates require orgs.write.

Read organization context

Three read endpoints, all cursor-paginated where they return lists:

# Your customer organizations
curl "https://api.liberty91.com/api/v1/organizations/" \
  -H "X-API-Key: $LIBERTY91_API_KEY"
 
# One organization's assets
curl "https://api.liberty91.com/api/v1/organizations/{org_id}/assets/" \
  -H "X-API-Key: $LIBERTY91_API_KEY"
 
# One organization's suppliers
curl "https://api.liberty91.com/api/v1/organizations/{org_id}/suppliers/" \
  -H "X-API-Key: $LIBERTY91_API_KEY"

Assets and suppliers are distinct in the platform: assets cover the organization's own estate, including the technologies it runs, while suppliers are the third parties it depends on. Keeping both current is what makes supply-chain and relevance analysis work (see Supply chain).

Upload a document for extraction

Rather than entering assets and suppliers by hand, you can upload the documents that already describe them (asset inventories, vendor lists, architecture overviews) and let the platform extract candidates:

curl -X POST "https://api.liberty91.com/api/v1/organizations/{org_id}/documents/" \
  -H "X-API-Key: $LIBERTY91_API_KEY" \
  -F "file=@vendor-list-2026.xlsx"

Accepted types: PDF, TXT, CSV, XLSX, XLS, DOCX, PPTX, up to 10 MB. Upload costs 25 credits and starts extraction in the background.

The extraction workflow

Upload the document. Note the document ID in the response.
Poll GET /api/v1/organizations/{org_id}/documents/{doc_id}/ and watch extraction_status move from pending through processing to completed (or failed).
Review the extracted candidate entities in the document detail.
Confirm the ones you want with POST /api/v1/organizations/{org_id}/documents/{doc_id}/entities/confirm/. Only then are assets and suppliers written to the organization, and enrichment starts for the new entries.

The confirm step is deliberate: nothing lands in an organization's profile until you have explicitly confirmed it. Confirming costs 5 credits.

Refresh an entity's description

Suppliers and asset technologies carry platform-written descriptions and analysis. When you know something changed (a supplier was acquired, a technology moved versions), you can trigger a refresh:

curl -X POST "https://api.liberty91.com/api/v1/entities/{entity_type}/{entity_id}/update-description/" \
  -H "X-API-Key: $LIBERTY91_API_KEY"

entity_type is supplier or asset-technology. The call returns immediately; poll the entity's analysis_status field, which moves from analyzing to ready. A refresh costs 10 credits.

Frequently asked questions

How does document upload and extraction work in the API?

POST a document to an organization's documents endpoint. The platform extracts candidate assets and suppliers from it in the background; you poll the document's extraction status, review what was found, and confirm the entities you want written to the organization.

What file types can I upload for extraction?

PDF, TXT, CSV, XLSX, XLS, DOCX, and PPTX, up to 10 MB per document.

Are extracted assets and suppliers added automatically?

No. Extraction only produces candidates. Nothing is written to the organization until you call the confirm endpoint, so you stay in control of the organization's profile.

Was this page helpful?

← PreviousAlerts: rules and matches Next →User roles and permissions