Skip to main content
Metal’s data model centers on a few core resources that reference each other. Understanding how they relate makes the API easier to use.

Core resources

Company

An entity your firm tracks: an operating company, investor, advisor, or service provider.

Deal

An opportunity in your pipeline, usually tied to a target company.

Person

A contact or executive, optionally linked to a company.

Identifiers

Every resource has a Metal-assigned id (a 24-character hex string). You can also attach your own identifiers so you can reconcile records with external systems: Companies, deals, and people can be fetched by external identifier as well as by Metal id. For example:

Companies

A company is the most central resource. The only required field on creation is canonicalName.
Fields marked Enriched are populated by Metal from your documents, data providers, and the web, then reconciled into a single value. The enrichment object exposes the alternatives and their sources for each one.

Deals

A deal represents an opportunity. It usually points at a target company via companyId.
Metal models deal status and stage with two layers: a fixed set of internal values (used for logic) and your firm’s own custom labels (shown in the app). The API returns both the internal status/stage and the external labels where configured.

People

A person is a contact, often linked to a company through the company field.

Relationships

  • A deal references a target company through companyId.
  • A person references their company through company.
  • Documents are attached to companies and deals and become searchable once ingested.

Reading collections

List endpoints (GET /v1/companies, GET /v1/deals, GET /v1/people) return arrays under data and support pagination. For relevance-ranked retrieval, use the search endpoints instead.