Endpoints

All endpoints are prefixed with https://api-rest.tendios.com/api and require the api-key header.

Context

Get caller context

http

GET /v1/whoami

Returns who the calling API key belongs to. Useful as a first call to confirm a key is wired up correctly and to discover the account and organization it resolves to — you never pass an account id to the other endpoints, so this is how you find out which account you're acting on.

Response

Field	Type	Description
`principal.type`	`string`	Always `apiKey`
`principal.id`	`string`	ID of the key making the call
`principal.name`	`string`	The name you gave the key, e.g. `Claude integration`
`account.id`	`string`	Account the key belongs to
`account.name`	`string`	Account name
`account.slug`	`string`	Account slug
`organization`	`object \| null`	`{ id, name }` of the linked organization, if any
`plan.tier`	`string \| null`	Active Bid plan tier, e.g. `tier_2`

Example

bash

curl https://api-rest.tendios.com/api/v1/whoami \
  -H "api-key: tend_your_key"

Tenders

Search tenders

http

POST /v1/tenders/search

Returns a paginated list of tenders matching the given filters. It reads data, so read-only keys can call it.

Request body — the most common fields. Every filter is optional; see Filtering for the full list (status, CPVs, procedures, amounts, discount rate, prorated budgets and every date range).

Field	Type	Description
`text`	`string`	Free-text search query
`page`	`number`	Page number (default: 1)
`pageSize`	`number`	Results per page (max 100, default: 10)
`sort`	`string`	Sort field (default: `by-published-date`) — see Sorting
`isDescendent`	`boolean`	Sort descending (default: `true`)
`status`	`string[]`	Filter by status values
`locations`	`string[]`	Location filters: `country/<ISO-2>` or `town/<name>`, e.g. `["country/ES", "town/Madrid"]`
`minBudget`	`number`	Minimum budget (no taxes)
`maxBudget`	`number`	Maximum budget (no taxes)

Example

bash

curl -X POST https://api-rest.tendios.com/api/v1/tenders/search \
  -H "api-key: tend_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "text": "IT services", "pageSize": 10, "locations": ["country/ES"] }'

Response — see Pagination for the envelope shape.

Get tender by ID

http

GET /v1/tenders/{id}

Returns the full detail of a single tender.

Path params

Param	Description
`id`	Tender ID (e.g. `507f1f77bcf86cd799439011`)

Example

bash

curl https://api-rest.tendios.com/api/v1/tenders/507f1f77bcf86cd799439011 \
  -H "api-key: tend_your_key"

Get tender sheets

http

GET /v1/tenders/{id}/sheets

Returns all document sheets attached to a tender.

Path params

Param	Description
`id`	Tender ID

Document classification

Every sheet carries a read-only documentType attribute with the procurement document type Tendios resolved for it:

code — stable machine-readable value from the closed list below. Safe to compare literally.
label — human-readable name (Spanish), ready to display. Do not branch on it.

documentType is always present, but it is null when the document has no classification. Coverage is not guaranteed for older documents, so your integration must handle null. An unclassified document is returned normally and keeps its isPliego value.

`code`	`label`
`pcap`	PCAP
`ppt`	PPT
`documento_pliegos`	Documento de pliegos
`annex_pcap`	Anexo PCAP
`annex_ppt`	Anexo PPT
`annex`	Anexo
`cuadro`	Cuadro de características
`memoria`	Memoria justificativa
`necesidades`	Informe de necesidades
`estudio_viabilidad`	Estudio de viabilidad
`aprobacion`	Aprobación del expediente
`anuncio`	Anuncio
`acta`	Acta
`informe_valoracion`	Informe de valoración
`adjudicacion`	Adjudicación

If Tendios reclassifies a document, later reads return the updated value. No notification is sent.

Example response

json

[
  {
    "id": "507f1f77bcf86cd799439011",
    "name": "PCAP.pdf",
    "url": "https://contrataciondelestado.es/.../PCAP.pdf",
    "isDownloaded": true,
    "tenderId": "507f1f77bcf86cd799439013",
    "isPliego": true,
    "documentType": { "code": "pcap", "label": "PCAP" },
    "ragProcessed": true
  },
  {
    "id": "507f1f77bcf86cd799439012",
    "name": "Documento_2019.pdf",
    "url": "https://contrataciondelestado.es/.../Documento_2019.pdf",
    "isDownloaded": false,
    "tenderId": "507f1f77bcf86cd799439013",
    "isPliego": false,
    "documentType": null,
    "ragProcessed": false
  }
]

Get tender questions and answers

http

GET /v1/tenders/{id}/questions-answers

Returns the PLACE questions and answers (clarifications) for a tender.

Path params

Param	Description
`id`	Tender ID

Query params

Param	Type	Default	Description
`page`	`number`	1	Page number
`pageSize`	`number`	20	Results per page (maximum 100)

Response

Field	Type	Description
`questionsAndAnswersActive`	`boolean`	Whether PLACE has an active clarifications channel
`items`	`object[]`	Questions and answers for the requested page
`items[].id`	`string`	Stable Tendios identifier for the clarification
`items[].question`	`string`	Question submitted through PLACE
`items[].answer`	`string?`	Answer from the contracting authority, if available
`items[].publishedAt`	`date-time`	Publication timestamp on PLACE
`items[].reference`	`string?`	PLACE reference; currently always `null`
`items[].attachments`	`object[]`	Attached files; currently always empty
`pagination`	`object`	`{ total, page, limit, hasPreviousPage, hasNextPage }`

Errors — 404 if the tender doesn't exist.

Get tender candidates

http

GET /v1/tenders/{id}/candidates

Returns the companies Tendios holds as having presented to an awarded tender, which of them won, which lots each winner won and the documents the records were extracted from. Offers, scores and the reasons a company lost are not included.

Coverage

Most awarded tenders have no candidate records. The identities of non-winning bidders are not published as structured data: they only appear in the award board minutes (actas), which are published for roughly a quarter of tenders. In mid-2026 about 6% of the tenders awarded each month have candidate records, and coverage is growing. The number of offers received (offersReceived) is available far more often, so expect a response like "no identities, but eight offers were received" for most tenders.

Path params

Param	Description
`id`	Tender ID

Query params

Param	Type	Default	Description
`page`	`number`	1	Page number
`pageSize`	`number`	20	Results per page (maximum 100). Use `1` to read only the counts in the header

Response

Field	Type	Description
`candidatesCount`	`number`	Companies Tendios holds as having presented. `0` means Tendios holds no record, not that nobody bid
`offersReceived`	`number?`	Offers received, from the structured award data. `null` when unknown; `0` only when nobody bid
`adjudicatedAt`	`date-time?`	Award date of the tender. `null` when the tender is not awarded or the source does not publish it
`sources`	`object[]`	Documents the records were extracted from: `{ sheetId, name, url, date }`. See Get tender sheets
`items`	`object[]`	Candidates for the requested page: winners first, then by name
`items[].organizationId`	`string`	Unique Tendios organization id. Use it with Get organization to pull its award history
`items[].name`	`string?`	Legal name
`items[].taxId`	`string?`	CIF/NIF
`items[].won`	`boolean`	Whether the company won the tender or any of its lots
`items[].lotsWon`	`object[]?`	Lots won: `{ id, lotId, name, adjudicatedAt }`. `null` when the company did not win; empty when the tender has no lots
`items[].sourceSheetIds`	`string[]`	`sheetId` of the documents this candidate was extracted from
`pagination`	`object`	`{ total, page, limit, hasPreviousPage, hasNextPage }`

Identify companies by organizationId, never by slug. Slugs are not unique: clece-sa is shared by three organizations with different tax IDs.
Winners are reconciled against the tender. A company is marked as winner when its record says so or when it is the awardee of the tender or of one of its lots. The awardee and award amount of the tender itself are not changed by this endpoint.
A company that won several lots appears once, with every lot in lotsWon. Non-winners are never attributed to a lot.
There is no lot-level award date in most sources: use the adjudicatedAt of the tender.
A tender without an award returns an empty list, not an error.

Errors — 404 if the tender doesn't exist.

Get tender contacts

http

GET /v1/tenders/{id}/contacts

Returns contacts of the tender's contracting body, gathered from DIR3 (the Spanish public administration directory), the contacts Tendios holds for that organization, signatures and the text of the tender's documents, plus email candidates inferred from metadata and clearly marked as such.

Path params

Param	Description
`id`	Tender ID

Query params

Param	Type	Default	Description
`minDir3Relevance`	`number`	30	Keep DIR3-only emails whose relevance percentage is strictly greater than this. Unscored DIR3-only emails are excluded; emails with any other source are always kept

Response — an array of contacts:

Field	Type	Description
`email`	`string`	Email address
`name`	`string \| null`	Contact name; `null` when unknown
`jobTitle`	`string \| null`	Explicitly recorded role of the contact; `null` when unknown
`phone`	`string \| null`	Phone number; `null` when unknown
`status`	`string`	`FOUND`: observed in a source. `INFERRED`: unverified candidate built from a name and an observed address pattern
`sources`	`object[]`	Where the contact was found
`inference`	`object \| null`	Why the address was inferred, when an inference supports it; `null` otherwise

Neither status verifies that the mailbox exists.

Stored contacts belong to the exact contracting body of the tender. Organizations sharing its tax ID are not combined.
DIR3 matches by tax ID and may include other administrative units that share it. DIR3 relevance measures how relevant a unit is to procurement, not a link to this specific contracting body.
Emails from the tender's documents are included only when stored contacts or DIR3 show that the contracting body owns the email domain, with no conflicting owner. Shared or unproven domains are excluded.
Document names and job titles are persisted for newly processed documents when the text explicitly links a person to an email. They are taken from this tender's documents, so a shared mailbox does not inherit a person from another tender. Unknown or ambiguous details are returned as null. Historical records are not backfilled; querying this endpoint does not trigger extraction.

Rate limit — this endpoint has its own budget of 60 requests per minute per account (or the key's own limit, if lower).

Errors — 404 if the tender doesn't exist, 429 when the rate limit is exceeded (see the Retry-After header).

Download tender sheet

http

GET /v1/tenders/sheets/{sheetId}/download

Downloads a single tender document file.

Path params

Param	Description
`sheetId`	Sheet ID

Download via short-lived link

http

GET /v1/tenders/documents/{token}/download

Downloads a tender document using a short-lived, pre-signed token instead of a sheet id. This is the form the MCP get_tender_sheets tool hands back, so an assistant can surface a working download link without streaming bytes through a tool result.

Path params

Param	Description
`token`	Short-lived token identifying the file

Organizations

Get organization profile

http

GET /v1/organizations/{idOrSlug}

Returns the public profile of an organization (bidder or contracting body).

Path params

Param	Description
`idOrSlug`	Organization id (e.g. the `contractingOrganizationId` of a tender) or slug (e.g. `altia-consultores-sa`). Both resolve the same organization and response

Response fields

Field	Type	Description
`id`	`string`	Organization ID
`name`	`string`	Organization name
`type`	`string`	`bidder` or `public-contracting-institution`
`taxId`	`string?`	Tax identification number
`activity`	`string?`	Business activity description
`country`	`string?`	ISO 3166-1 alpha-2 country code
`address`	`object?`	`{ city, province, postCode, street }`
`webUrl`	`string?`	Website URL
`logo`	`string?`	Logo image URL

Example

bash

# By slug
curl https://api-rest.tendios.com/api/v1/organizations/altia-consultores-sa \
  -H "api-key: tend_your_key"

# By id — e.g. the contractingOrganizationId returned by the tender endpoints
curl https://api-rest.tendios.com/api/v1/organizations/507f1f77bcf86cd799439012 \
  -H "api-key: tend_your_key"

Get organization award statistics

http

GET /v1/organizations/{idOrSlug}/awards

Returns yearly award statistics and sector breakdown for an organization.

Path params

Param	Description
`idOrSlug`	Organization id (e.g. the `contractingOrganizationId` of a tender) or slug, same as the above

Response fields

Field	Type	Description
`organizationId`	`string`	Organization ID
`organizationName`	`string`	Organization name
`type`	`string`	`bidder` or `public-contracting-institution`
`stats`	`array`	Yearly stats: `[{ year, count, totalAmount }]`
`sectors`	`array`	CPV sector breakdown: `[{ divisionCode, divisionNameEn, divisionNameEs, emoji, count, percentage }]`

Example

bash

curl https://api-rest.tendios.com/api/v1/organizations/altia-consultores-sa/awards \
  -H "api-key: tend_your_key"

# Or by id
curl https://api-rest.tendios.com/api/v1/organizations/507f1f77bcf86cd799439012/awards \
  -H "api-key: tend_your_key"

Market intelligence

Get market awards

http

POST /v1/market-awards

Returns the tenders awarded to a curated supplier family (a company and its related entities), by a buyer, or both, within a publication or award date range, with totals. It reads data, so read-only keys can call it.

Supplier families and buyer perimeters are curated by Tendios. Ask support@tendios.com for the IDs you need; MCP clients can list them with the list_market_scopes tool.

Request body

Field	Type	Default	Description
`supplierFamilyId`	`string`	—	Curated supplier family. Omit to count awards to any supplier; then `buyerPerimeterId` or `buyerOrganizationId` is required
`buyerPerimeterId`	`string`	—	Curated buyer perimeter. Omit to include every buyer within the countries your account can access
`buyerOrganizationId`	`string`	—	Tendios organization ID of a buyer without a curated perimeter. Cannot be combined with `buyerPerimeterId`
`includeBuyerDependents`	`boolean`	`true`	With `buyerOrganizationId`, also count its dependent bodies
`countryCode`	`string`	—	Two-letter tender-location country code, e.g. `ES`; restricted to the countries your account can access
`publishedFrom`	`date`	—	Publication date lower bound, inclusive (`YYYY-MM-DD`)
`publishedTo`	`date`	—	Publication date upper bound, inclusive
`awardedFrom`	`date`	—	Award date lower bound, inclusive (`YYYY-MM-DD`)
`awardedTo`	`date`	—	Award date upper bound, inclusive
`includeModifications`	`boolean`	`false`	Also include contract modifications
`page`	`number`	1	Page number
`pageSize`	`number`	50	Results per page (maximum 100)
`sortBy`	`string`	`published_at`	`published_at` or `awarded_at`
`sortDirection`	`string`	`asc`	`asc` or `desc`

A publication range or an award range is required, and each range needs both of its bounds.

Response

Field	Type	Description
`items`	`object[]`	Awarded tenders: `{ tenderId, title, expedient, buyer, awardee, publishedAt, awardedAt, status, awardAmount, currency, isModification }`. `buyer` and `awardee` are `{ id, name }`
`pagination`	`object`	`{ page, pageSize, total, hasNextPage }`
`summary`	`object`	`{ totalContracts, awardedAmountByCurrency: [{ currency, amount }] }` for every matching award, not only the page
`appliedDefinition`	`object`	What was applied: `supplierFamilyId`, `buyerPerimeterId`, `buyerOrganizationId`, `includeBuyerDependents`, `buyerOrganizationCount`, `published`, `awarded`, `countryCode` and the `version` of the curated scopes used

Example

bash

curl -X POST https://api-rest.tendios.com/api/v1/market-awards \
  -H "api-key: tend_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "supplierFamilyId": "your-supplier-family-id",
    "countryCode": "ES",
    "publishedFrom": "2025-01-01",
    "publishedTo": "2025-12-31",
    "sortBy": "awarded_at",
    "sortDirection": "desc"
  }'

CPV codes

Get CPV details

http

GET /v1/cpv/{code}

Returns details for a CPV code including names in 7 EU languages.

Path params

Param	Description
`code`	CPV code (e.g. `72000000`)

Response fields

Field	Type	Description
`code`	`string`	CPV code
`type`	`string`	`division` \| `group` \| `class` \| `category`
`nameEn`	`string?`	Name in English
`nameEs`	`string?`	Name in Spanish
`nameFr`	`string?`	Name in French
`nameDe`	`string?`	Name in German
`nameIt`	`string?`	Name in Italian
`nameCa`	`string?`	Name in Catalan
`namePt`	`string?`	Name in Portuguese
`emoji`	`string?`	Emoji representing the category
`fontAwesomeIcon`	`string?`	Font Awesome icon name

Example

bash

curl https://api-rest.tendios.com/api/v1/cpv/72000000 \
  -H "api-key: tend_your_key"

Alerts

Alerts belong to the account that owns the API key. You never pass an account id — it is resolved from the key.

List alerts

http

GET /v1/alerts

Returns a paginated list of every alert configured for the account, with a total count.

Query params

Param	Type	Default	Description
`text`	`string`	—	Filter alerts by title
`isArchived`	`boolean`	—	Filter archived or non-archived
`page`	`number`	1	Page number
`pageSize`	`number`	20	Alerts per page (max 100)
`sort`	`string`	`by-update-date`	See alert sort values
`sortDirection`	`string`	`desc`	`asc` or `desc`

Get an alert

http

GET /v1/alerts/{alertId}

Returns the full configuration of one alert.

Path params

Param	Description
`alertId`	Alert ID

Response

Field	Type	Description
`id`	`string`	Alert ID
`title`	`string`	Alert title
`description`	`string?`	Optional description
`platformUrl`	`string`	URL to open the alert in Bid
`criteria`	`object`	Tender matching criteria (see below)
`notificationConfig`	`object`	Schedule and delivery configuration
`responsibles`	`object[]`	Users responsible for the alert
`isActive`	`boolean`	Whether the alert is running
`isPublic`	`boolean`	Whether all account users can access it
`isArchived`	`boolean`	Whether the alert is archived
`isAutoConfigured`	`boolean`	Whether Tendios generated the configuration
`createdBy`	`string`	ID of the creator
`createdAt`	`date-time`	Creation timestamp
`updatedAt`	`date-time`	Last update timestamp
`lastNotifiedAt`	`date-time`	Last time the alert matched
`lastNotificationSentAt`	`date-time?`	Last time an email went out

Create an alert

http

POST /v1/alerts

Creates an alert and returns it. Responds 201.

Request body

Field	Type	Required	Description
`title`	`string`	Yes	Alert title
`windowsSearch`	`object[]`	Yes	Events that trigger the alert (min 1) — see below
`description`	`string`	No	Free-text description
`criteria`	`object`	No	Tender matching criteria — see below
`notificationConfig`	`object`	No	Schedule and delivery — see below
`responsibles`	`object[]`	No	`{ id, receiveEmails }` per recipient
`isActive`	`boolean`	No	Start active (default `true`)
`isPublic`	`boolean`	No	Visible to all account users (default `true`)

windowsSearch[] — which tender event the alert watches:

Field	Type	Description
`field`	`string`	`expedientPublishedAt`, `expedientAdjudicationDate`, or `expedientExpirationDate`
`expirationOffset`	`number`	Days before expiry to notify — only for `expedientExpirationDate` (min 1)
`withExtension`	`boolean`	Use the extended deadline — only for `expedientExpirationDate`

criteria — every field optional:

Field	Type	Description
`keywords`	`object`	`{ include: string[], exclude: string[] }`
`cpvCodes`	`object`	`{ include: string[], exclude: string[] }`
`locations`	`object`	`{ country: {include,exclude}, province: {include,exclude} }`
`budget`	`object`	`{ min, max }`
`statuses`	`string[]`	Tender status values, e.g. `["Publicada"]` (min 1 when present)
`contractTypes`	`string[]`	Contract type values
`procedures`	`string[]`	Procedure type values
`inDeadline`	`boolean`	Only tenders still open for submission

notificationConfig — every field optional:

Field	Type	Description
`frequency`	`object`	`{ type: "daily", weekdays: number[] }` or `{ type: "weekly", dayOfWeek: number }` — 1 = Monday, 7 = Sunday
`hour`	`number`	Delivery hour, `0`–`23`
`timezone`	`string`	IANA zone, e.g. `Europe/Madrid`
`attachments`	`object`	`{ hasPdf, hasCsv, hasXlsx }`
`includeModifications`	`boolean`	Include modified tenders, not just new ones
`sendWithoutItems`	`boolean`	Send the email even when nothing matched

Example

bash

curl -X POST https://api-rest.tendios.com/api/v1/alerts \
  -H "api-key: tend_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "IT services in Madrid",
    "windowsSearch": [{ "field": "expedientPublishedAt" }],
    "criteria": {
      "keywords": { "include": ["software"] },
      "locations": { "province": { "include": ["28"] } },
      "budget": { "min": 50000 }
    },
    "notificationConfig": {
      "frequency": { "type": "daily", "weekdays": [1, 2, 3, 4, 5] },
      "hour": 8,
      "timezone": "Europe/Madrid"
    }
  }'

Update an alert

http

PATCH /v1/alerts/{alertId}

Updates selected fields and returns the alert. Responds 200. Every field is optional — omitted fields are left unchanged.

Path params

Param	Description
`alertId`	Alert ID

Request body — the same fields as Create an alert, all optional, plus:

Field	Type	Description
`isArchived`	`boolean`	Archive or unarchive

Get alert tender results

http

POST /v1/alerts/{alertId}/results

Returns tenders that match a saved alert. It reads data, so read-only keys can call it.

Path params

Param	Description
`alertId`	Alert ID

Request body — every field is optional and narrows the alert's own criteria.

Field	Type	Default	Description
`page`	`number`	1	Page number (1-based)
`pageSize`	`number`	10	Results per page (maximum 100)
`text`	`string`	—	Extra full-text filter on top of the alert criteria
`minPublicationDate`	`date-time`	—	Published on or after
`maxPublicationDate`	`date-time`	—	Published on or before
`minLastSignificantChangeDate`	`date-time`	—	Last significant change on or after
`maxLastSignificantChangeDate`	`date-time`	—	Last significant change on or before
`sort`	`string`	`by-published-date`	Any tender sort value
`isDescendent`	`boolean`	`true`	Sort in descending order

The response is the same paginated tender list as Search tenders.

Alert sort values

Accepted by sort on List alerts. Default by-update-date.

Value	Sorts by
`by-name`	Alert title
`by-update-date`	Last update date
`by-creation-date`	Creation date
`by-last-notified-date`	Last time the alert matched
`by-last-notification-sent-date`	Last time an email was sent
`by-status`	Active/inactive state

Pipelines

List pipelines

http

GET /v1/pipelines

Returns the opportunity pipelines configured for the account, each with its stages. Call this first to get the pipelineId and statusId values the Kanban and Opportunities endpoints need.

Query params

Param	Type	Default	Description
`page`	`number`	1	Page number
`pageSize`	`number`	20	Pipelines per page (max 100)

Response — paginated list of:

Field	Type	Description
`id`	`string`	Pipeline ID
`name`	`string`	Pipeline name
`statuses`	`object[]`	Stages — see below

statuses[]

Field	Type	Description
`id`	`string`	Stage ID
`name`	`string`	Stage name
`isInitial`	`boolean`	Whether new opportunities land here
`isTerminal`	`boolean`	Whether reaching this stage closes the opportunity
`outcomeType`	`string`	Outcome the stage represents
`sortPoints`	`number`	Board ordering weight
`showInKanban`	`boolean`	Whether the stage renders as a column
`description`	`string?`	Optional stage description

Kanban

These endpoints expose the CRM pipeline kanban board. They require the API key of the account that owns the pipeline.

Get pipeline status totals

http

GET /v1/kanban/{pipelineId}/status

Returns opportunity counts and total amounts grouped by pipeline status — used to render kanban column headers.

Path params

Param	Description
`pipelineId`	Pipeline ID

Query params

Param	Type	Description
`responsible`	`string[]`	Filter by responsible user IDs
`teamResponsible`	`string[]`	Filter by responsible team IDs

Response — array of:

Field	Type	Description
`status`	`object`	`{ id, name, isInitial, isTerminal, pipelineId, outcomeType, sortPoints, showInKanban, backgroundColor?, textColor?, description? }`
`opportunityCount`	`number`	Number of opportunities in this status
`totalAmount`	`number`	Sum of opportunity amounts
`currency`	`string`	Currency code (e.g. `EUR`)

Get opportunities by status

http

GET /v1/kanban/{pipelineId}/status/{statusId}/opportunities

Returns paginated opportunities for a single kanban column.

Path params

Param	Description
`pipelineId`	Pipeline ID
`statusId`	Pipeline status ID

Query params

Param	Type	Default	Description
`page`	`number`	1	Page number
`pageSize`	`number`	10	Results per page
`sort`	`string`	—	Sort order: `custom`, `by-update-date`, `by-due-date`, `by-budget`, `by-prorated-budget`
`sortDirection`	`string`	`asc`	`asc` or `desc`

Search kanban opportunities

http

GET /v1/kanban/{pipelineId}/search

Searches opportunities across all statuses in a pipeline. Returns a map of statusId → opportunities[].

Path params

Param	Description
`pipelineId`	Pipeline ID

Query params

Param	Type	Default	Description
`search`	`string`	—	Text search term
`limit`	`number`	10	Max opportunities per status (max 50)
`responsible`	`string[]`	—	Filter by responsible user IDs
`teamResponsible`	`string[]`	—	Filter by responsible team IDs
`sort`	`string`	—	Sort order: `custom`, `by-update-date`, `by-due-date`, `by-budget`, `by-prorated-budget`
`sortDirection`	`string`	`asc`	`asc` or `desc`

Opportunities

These endpoints act on individual opportunities in the account's CRM pipeline. Get the IDs they need from List pipelines and the Kanban endpoints.

Move an opportunity to another status

http

PUT /v1/opportunities/{opportunityId}/status

Moves an opportunity to a different stage of its current pipeline. Responds 204 — including when the opportunity is already in the requested stage, which makes the call safe to retry.

Path params

Param	Description
`opportunityId`	Opportunity ID

Request body

Field	Type	Required	Description
`targetStatusId`	`uuid`	Yes	Target pipeline stage ID

Moving to a terminal stage closes the opportunity

Stages with isTerminal: true (see List pipelines) end the opportunity's lifecycle. There is no undo through the API — check isTerminal before moving if that isn't what you intend.

Errors — 403 if the opportunity belongs to another account, 404 if the opportunity or stage doesn't exist.

Get opportunity questions and answers

http

GET /v1/opportunities/{opportunityId}/questions-answers

Returns the PLACE questions and answers (clarifications) for the tender linked to an opportunity. The opportunity must belong to the account associated with the API key.

Path params

Param	Description
`opportunityId`	Opportunity ID

Query params

Param	Type	Default	Description
`page`	`number`	1	Page number
`pageSize`	`number`	20	Results per page (maximum 100)

Response

Field	Type	Description
`questionsAndAnswersActive`	`boolean`	Whether PLACE has an active clarifications channel
`items`	`object[]`	Questions and answers for the requested page
`items[].id`	`string`	Stable Tendios identifier for the clarification
`items[].question`	`string`	Question submitted through PLACE
`items[].answer`	`string?`	Answer from the contracting authority, if available
`items[].publishedAt`	`date-time`	Publication timestamp on PLACE
`items[].reference`	`string?`	PLACE reference; currently always `null`
`items[].attachments`	`object[]`	Attached files; currently always empty
`pagination`	`object`	`{ total, page, limit, hasPreviousPage, hasNextPage }`

Errors — 403 if the opportunity belongs to another account, 404 if it doesn't exist.

Get opportunity candidates

http

GET /v1/opportunities/{opportunityId}/candidates

Returns the candidates of the tender linked to an opportunity, with the same response and coverage caveats as Get tender candidates. An opportunity on a lot returns the candidates of its whole tender. An opportunity not linked to a tender returns an empty response. The opportunity must belong to the account associated with the API key.

Path params

Param	Description
`opportunityId`	Opportunity ID

Query params — same as Get tender candidates.

Errors — 404 if the opportunity doesn't exist or belongs to another account.

Get workflow actions

http

GET /v1/opportunities/{opportunityId}/workflow-actions

Returns the current workflow action records for an opportunity, grouped by workflow step. Use it to see which qualification steps have been completed and which are outstanding.

Path params

Param	Description
`opportunityId`	Opportunity ID

Response — array of:

Field	Type	Description
`id`	`string`	Action ID
`workflowStepId`	`string`	Step the action belongs to
`workflowStepName`	`string?`	Step name
`workflowStepPosition`	`number?`	Step position in the workflow
`name`	`string`	Action name
`targetType`	`string`	What the action targets
`targetId`	`string?`	ID of the target, when applicable
`status`	`string`	Action status
`position`	`number`	Position within the step
`completedAt`	`date-time?`	When it was completed
`createdAt`	`date-time`	Creation timestamp
`updatedAt`	`date-time`	Last update timestamp

Errors — 403 if the opportunity belongs to another account, 404 if it doesn't exist.

List opportunity tasks

http

GET /v1/opportunities/{opportunityId}/tasks

Returns a paginated list of tasks attached to an opportunity.

Path params

Param	Description
`opportunityId`	Opportunity ID

Query params

Param	Type	Default	Description
`status`	`string`	—	Filter by `to-do`, `in-progress`, or `done`
`page`	`number`	1	Page number
`pageSize`	`number`	20	Tasks per page (max 100)

Create an opportunity task

http

POST /v1/opportunities/{opportunityId}/tasks

Creates a task on an opportunity. Responds 201 with the new task's id.

Path params

Param	Description
`opportunityId`	Opportunity ID

Request body

Field	Type	Required	Description
`title`	`string`	Yes	Task title
`description`	`string`	No	Task description
`status`	`string`	No	`to-do` (default), `in-progress`, or `done`
`priority`	`string`	No	`high`, `medium` (default), or `low`
`userIds`	`string[]`	No	Account user IDs assigned to the task
`deadlineAt`	`date-time`	No	ISO 8601 deadline

Example

bash

curl -X POST https://api-rest.tendios.com/api/v1/opportunities/{opportunityId}/tasks \
  -H "api-key: tend_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "title": "Prepare technical proposal", "priority": "high", "deadlineAt": "2026-09-01T09:00:00.000Z" }'

Errors — 404 if the opportunity doesn't exist.

List opportunity summaries

http

GET /v1/opportunities/{opportunityId}/summaries

Returns the AI-generated summaries for an opportunity.

Path params

Param	Description
`opportunityId`	Opportunity ID

Response — array of:

Field	Type	Description
`id`	`string`	Summary ID
`name`	`string`	Summary name
`status`	`string`	`pending`, `in_progress`, `completed`, or `failed`
`result`	`string?`	Rendered content in Markdown, present once `completed`
`generatedAt`	`date-time?`	When the summary finished generating
`createdAt`	`date-time`	Creation timestamp
`updatedAt`	`date-time`	Last update timestamp

Errors — 404 if the opportunity doesn't exist.

Download a summary PDF

http

GET /v1/opportunities/{opportunityId}/summaries/{summaryId}/pdf

Downloads a summary as a PDF. Only available once the summary's status is completed.

Path params

Param	Description
`opportunityId`	Opportunity ID
`summaryId`	Summary ID

Response — binary application/pdf, streamed with Content-Disposition: attachment.

Example

bash

curl https://api-rest.tendios.com/api/v1/opportunities/{opportunityId}/summaries/{summaryId}/pdf \
  -H "api-key: tend_your_key" \
  --output summary.pdf

Errors — 404 if the opportunity or summary doesn't exist, 409 (code SUMMARY_NOT_READY) if the summary hasn't finished generating yet.

API Key

Get API key info

http

GET /v1/api-key

Returns metadata about the API key in use — rate limit, expiry, last usage.

Example

bash

curl https://api-rest.tendios.com/api/v1/api-key \
  -H "api-key: tend_your_key"

Endpoints ​

Context ​

Get caller context ​

Tenders ​

Search tenders ​

Get tender by ID ​

Get tender sheets ​

Get tender questions and answers ​

Get tender candidates ​

Get tender contacts ​

Download tender sheet ​

Download via short-lived link ​

Organizations ​

Get organization profile ​

Get organization award statistics ​

Market intelligence ​

Get market awards ​

CPV codes ​

Get CPV details ​

Alerts ​

List alerts ​

Get an alert ​

Create an alert ​

Update an alert ​

Get alert tender results ​

Alert sort values ​

Pipelines ​

List pipelines ​

Kanban ​

Get pipeline status totals ​

Get opportunities by status ​

Search kanban opportunities ​

Opportunities ​

Move an opportunity to another status ​

Get opportunity questions and answers ​

Get opportunity candidates ​

Get workflow actions ​

List opportunity tasks ​

Create an opportunity task ​

List opportunity summaries ​

Download a summary PDF ​

API Key ​

Get API key info ​

Endpoints

Context

Get caller context

Tenders

Search tenders

Get tender by ID

Get tender sheets

Get tender questions and answers

Get tender candidates

Get tender contacts

Download tender sheet

Download via short-lived link

Organizations

Get organization profile

Get organization award statistics

Market intelligence

Get market awards

CPV codes

Get CPV details

Alerts

List alerts

Get an alert

Create an alert

Update an alert

Get alert tender results

Alert sort values

Pipelines

List pipelines

Kanban

Get pipeline status totals

Get opportunities by status

Search kanban opportunities

Opportunities

Move an opportunity to another status

Get opportunity questions and answers

Get opportunity candidates

Get workflow actions

List opportunity tasks

Create an opportunity task

List opportunity summaries

Download a summary PDF

API Key

Get API key info