Data model
Understand TenderMetro record types, fields, identifiers, relationships and lifecycle details — one normalised structure across every country and source, used by search, AI responses, exports, integrations and workspace workflows.
Documentation
Where to start
Guides
Cross-record concepts: lifecycles, identifiers, roles, values, category systems and relationship patterns.
Jump to sectionData Types
The record types that appear in search, AI responses, workspace records, exports and MCP tool responses.
Jump to sectionAttributes
Shared field definitions — types, value semantics and export formats applied consistently across the platform.
Jump to sectionGuides
Data model guides
How TenderMetro records, identifiers, roles, values, category systems and lifecycle relationships fit together.
Record lifecycles
How a notice moves from open to closing soon, closed and awarded — and where each change appears in search, alerts, webhooks and the activity stream.
Identifiers & provenance
Every record keeps its source system, original reference and publication date, so you can always trace a record back to the publisher's own site.
Organisation roles
The same organisation can appear as a buyer on one record and a supplier on another. Profiles unify both roles with shared history.
Value semantics
Values are stored as published and converted to USD for comparison. Estimated values are flagged separately from published budgets.
Category systems
CPV, UNSPSC, NAICS and ISIC codes are retained as published and mapped to TenderMetro's normalised sector taxonomy for cross-market filtering.
Relationships
Opportunities link to buyers, awards, documents and pursuits; awards link buyers to suppliers — the graph behind profiles, reports and AI answers.
Deduplication
The same tender appearing on multiple portals is merged into one record, with the other copies kept as references and provenance retained.
Quality scoring
Completeness is measured per record and per source. Sources that fall below the quality bar are flagged and deactivated automatically.
Reference
Data Types
The core record types exposed through search, exports, the REST API and MCP tools.
Opportunity
A tender, RFP, call for proposals or expression of interest published by a buyer.
| Field | Type | Notes |
|---|---|---|
| title | text | As published, with English rendering where provided |
| buyer | reference | Links to the Buyer record |
| sector | enum | Normalised sector across all sources |
| categories | text[] | Source classification codes retained (CPV, UNSPSC, NAICS) |
| country / region | text | Place of performance where published |
| value_usd | numeric | Converted from published currency |
| deadline_at | timestamp | Submission deadline, UTC |
| status | enum | open · closing_soon · closed · awarded |
| source / reference | text | Provenance: origin source and its own ID |
Award
A contract award or published spend record, linked to buyer and supplier.
| Field | Type | Notes |
|---|---|---|
| opportunity | reference | Linked when the original notice is known |
| buyer | reference | Awarding organisation |
| supplier | reference | Links to the Company record |
| amount_usd | numeric | Awarded value, converted |
| awarded_at | date | Award or publication date, 2020 onwards |
| period | text | Contract duration where published |
Buyer
Any organisation that publishes tenders: ministries, authorities, agencies, corporates.
| Field | Type | Notes |
|---|---|---|
| name / slug | text | Stable profile identifier |
| country / region | text | Where the buyer operates |
| sector | enum | Primary purchasing sector |
| annual_spend_usd | numeric | Derived from linked awards |
| type | enum | Government · multilateral · private · institutional |
Company
A supplier that appears in award records, from global primes to first-time local winners.
| Field | Type | Notes |
|---|---|---|
| name / slug | text | Stable profile identifier |
| sectors | text[] | Derived from award history |
| country / region | text | Registered and delivering markets |
| awards | reference[] | Every award linked to the supplier |
Document
Notices, annexes and addenda attached to an opportunity.
| Field | Type | Notes |
|---|---|---|
| opportunity | reference | Parent record |
| title / kind | text | Notice · annex · addendum · clarification |
| url | text | Original publisher location |
| published_at | timestamp | As published |
Activity
The event stream: new notices, awards and status changes as they land.
| Field | Type | Notes |
|---|---|---|
| kind | enum | Notice published · award published · status change |
| subject | reference | Opportunity, award, buyer or company |
| occurred_at | timestamp | Drives realtime feeds and webhooks |
Shared fields
Attributes
Shared attribute definitions used across record types, export formats, the API and MCP tool responses.
| Attribute | Values | Applies to | Notes |
|---|---|---|---|
| Status | open · closing_soon · closed · awarded | Opportunity | Derived from deadlines and award links; recalculated on every source refresh. |
| Sector | Normalised taxonomy enum | Opportunity · Buyer · Company | Mapped from CPV, UNSPSC, NAICS and ISIC codes published by each source. |
| Value | Numeric, USD-converted | Opportunity · Award | Original currency and amount retained alongside the converted figure. |
| Country / region | ISO-aligned names | All records | Place of performance on notices; operating market on organisations. |
| Dates & times | UTC timestamps | All records | Deadlines keep the publisher's stated date and time; all storage is UTC. |
| Provenance | source · reference · published date | All records | Required on every record — no record enters the index without an origin. |
| Quality score | 0–100 percentage | Opportunity · Award | Completeness across required fields; feeds source health monitoring. |
| Export formats | CSV · Excel · JSON | All record types | The same fields shown on screen are what exports and the API return. |
FAQ
Questions
Can I get the original published record?
Yes. Every record keeps its source and reference, and documents link back to the publisher's own location.
How are duplicates decided?
Matching uses buyer, title, deadline and value together rather than reference alone, keeping the earliest publication as the origin.
Are field names stable?
Yes. Fields and enums are additive only; existing fields are never renamed or removed without notice.
Is bulk access available?
Volume and bulk access are available on the Enterprise plan — contact us with the scope you need.
Build on the index
Create a key in the developer portal and read the docs for REST, webhooks and MCP.