Documentation

TenderFit Workspace documentation

A practical reference for importing records, understanding the scoring response, and keeping data access within the published product boundary.

Quick start

  1. Open the workspace and try the bundled sample.
  2. Define sectors, keywords, exclusions, preferred states, organisation type, and optional value range.
  3. Paste JSON or CSV records, or choose a local file.
  4. Review the reasons and limitations for every result.
  5. Open the record's source URL before making a bid decision.

Open the workspace

Supported input fields

FieldRequiredMeaning
idYesStable record identifier, up to 120 characters.
titleYesPublished tender title, up to 120 characters.
organisationNoIssuing organisation.
departmentNoPublishing department.
stateNoPublished state or location signal.
categoryNoPublished category used in sector matching.
value_amountNoNumeric tender value in the record's stated currency context.
closing_atNoISO 8601 deadline used for closed and closing-soon flags.
source_urlNoOfficial-source link. Results without one carry an explicit warning.
eligibilityNoPublished signals such as MSME_EXEMPT.
sectorsNoPublished sector labels.

Evaluation request

The canonical endpoint is POST /v1/evaluate. Unknown fields are rejected. TenderFit does not accept an api_key field.

{
  "profile": {
    "sectors": ["IT Services"],
    "keywords": ["cloud", "software"],
    "exclude_keywords": ["construction"],
    "states": ["Karnataka"],
    "organisation_type": "msme",
    "minimum_value": 1000000,
    "maximum_value": 20000000
  },
  "tenders": [{
    "id": "notice-123",
    "title": "Cloud hosting and managed support",
    "state": "Karnataka",
    "category": "IT Services",
    "value_amount": 6200000,
    "closing_at": "2026-10-08T12:00:00Z",
    "source_url": "https://official-source.example/notice"
  }]
}

What the response contains

Each result returns the original tender, score out of 100, high/medium/low band, review recommendation, deadline flags, hours to close, five score reasons, and a limitations list. Counts summarise the batch.

Results are sorted to keep open high-fit and urgent records visible, but sorting does not change their score.

Request and scoring limits

  • 1 MB maximum request body.
  • 1–100 tender records per evaluation.
  • Up to 20 sectors, states, and excluded terms; up to 30 included keywords.
  • Strong fit begins at 70; medium fit begins at 40.
  • Closing soon means a published deadline from now through 72 hours.

Official-source verification

TenderFit is not an official tender source. Treat missing fields as unknown, not as proof that a requirement does not exist. Before acting, verify the notice, documents, amendments, eligibility, value, and deadline with the issuing authority.

For the exact weights and missing-data behavior, read the scoring methodology. For privacy boundaries, read the privacy policy.