TED API

https://docs.ted.europa.eu/api/latest/
Admin
TED API is a set of programmatic tools that enables developers to integrate with the TED ecosystem...
Tokens:8,882
Snippets:108
Trust Score:10
Update:1 week ago
Show doc for...
Tokens:
Raw
### Get active SDK versions with GET /v3/config/sdk-versions

Source: https://docs.ted.europa.eu/api/latest/developer-operations.html

Retrieves the current range of SDK versions supported by the TED Central Validation Service (CVS). All notices submitted to TED must conform to an active SDK version, and this endpoint helps developers align submissions with supported versions to avoid compatibility issues.

```http
GET /v3/config/sdk-versions
```

--------------------------------

### GET /v3/config/sdk-versions

Source: https://docs.ted.europa.eu/api/latest/developer-operations.html

Returns the current range of SDK versions supported by the TED Central Validation Service (CVS). This helps developers ensure that notices submitted through their applications use a compatible SDK version.

```APIDOC
## GET /v3/config/sdk-versions

### Description
Returns the current range of SDK versions supported by the TED Central Validation Service (CVS). This helps developers ensure that notices submitted through their applications use a compatible SDK version.

### Method
GET

### Endpoint
/v3/config/sdk-versions

```

--------------------------------

### Query Submitted Notices - GET /v3/notices/

Source: https://docs.ted.europa.eu/api/latest/publish.html

Use this operation to retrieve a paginated list of your submitted TED notices, filterable and sortable. Requires an API key and provides access only to your own submissions. Useful for synchronizing metadata such as publication status.

```http
GET /v3/notices/
Copied!
```

--------------------------------

### GET /v3/notices/

Source: https://docs.ted.europa.eu/api/latest/publish.html

Query submitted notices. This operation enables users to query the status and details of their TED notices, returning a paginated list of all their submitted notices, which can be filtered and sorted. Access is exclusive to the user's own submissions and requires an API key.

```APIDOC
## GET /v3/notices/

### Description
Query the status and details of submitted TED notices. Returns a paginated list of the user's own notices, which can be filtered and sorted. Access requires an API key.

### Method
GET

### Endpoint
/v3/notices/

### Parameters
#### Query Parameters
- **page** (integer) - Optional - Page number for pagination.
- **size** (integer) - Optional - Number of items per page.
- **sort** (string) - Optional - Sorting criteria.
- **filter** (string) - Optional - Filter criteria.

### Response
#### Success Response (200)
- **notices** (array) - List of submitted notices.
- **totalElements** (integer) - Total number of notices.
- **totalPages** (integer) - Total number of pages.

#### Response Example
{
  "notices": [],
  "totalElements": 0,
  "totalPages": 0
}
```

--------------------------------

### GET /v3/notices/{businessId}/validation-report

Source: https://docs.ted.europa.eu/api/latest/publish.html

Retrieve the validation report for a submitted notice. Every submitted eForms notice undergoes a validation process, and this operation returns the report generated during submission, allowing users to review and address any validation issues.

```APIDOC
## GET /v3/notices/{businessId}/validation-report

### Description
Retrieve the validation report for a submitted notice. This report is generated during the notice submission process and includes any validation issues identified.

### Method
GET

### Endpoint
/v3/notices/{businessId}/validation-report

### Parameters
#### Path Parameters
- **businessId** (string) - Required - The unique identifier of the notice.

### Response
#### Success Response (200)
- **report** (object) - The validation report content.

#### Response Example
{
  "report": {}
}
```

--------------------------------

### Retrieve Validation Report - GET /v3/notices/{businessId}/validation-report

Source: https://docs.ted.europa.eu/api/latest/publish.html

Use this operation to obtain the validation report generated during notice submission. Every submitted eForms notice undergoes validation, and a report is generated even if validation fails, allowing you to review and address issues.

```http
GET /v3/notices/{businessId}/validation-report
Copied!
```

--------------------------------

### POST /v3/notices/render-async

Source: https://docs.ted.europa.eu/api/latest/visualise.html

Renders XML procurement notices into user-friendly formats like PDF or HTML asynchronously. This operation is recommended for larger, more complex notices to prevent request time-outs.

```APIDOC
## POST /v3/notices/render-async

### Description
Renders XML procurement notices into user-friendly formats like PDF or HTML asynchronously. This operation is recommended for larger, more complex notices to prevent request time-outs.

### Method
POST

### Endpoint
/v3/notices/render-async

### Parameters
No parameters documented.

### Request Example
No request body documented.

### Response
No response schema documented.

### Response Example
No response example documented.
```

--------------------------------

### POST /v3/notices/render-async

Source: https://docs.ted.europa.eu/api/latest/visualise.html

Asynchronous endpoint to render larger, more complex notices, preventing request time-outs.

```http
POST /v3/notices/render-async
```

--------------------------------

### POST /v3/notices/render

Source: https://docs.ted.europa.eu/api/latest/visualise.html

Renders XML procurement notices into user-friendly formats like PDF or HTML. This synchronous operation is suitable for smaller notices.

```APIDOC
## POST /v3/notices/render

### Description
Renders XML procurement notices into user-friendly formats like PDF or HTML. This synchronous operation is suitable for smaller notices.

### Method
POST

### Endpoint
/v3/notices/render

### Parameters
No parameters documented.

### Request Example
No request body documented.

### Response
No response schema documented.

### Response Example
No response example documented.
```

--------------------------------

### POST /v3/notices/render

Source: https://docs.ted.europa.eu/api/latest/visualise.html

Synchronous endpoint to render a procurement notice into a user-friendly format. Use for smaller notices to avoid request time-outs.

```http
POST /v3/notices/render
```

--------------------------------

### POST /v3/notices/search

Source: https://docs.ted.europa.eu/api/latest/search.html

Search and retrieve published notices via expert queries and bulk downloads of notices in XML format. This endpoint is openly accessible without authentication.

```APIDOC
## POST /v3/notices/search

### Description
Search and retrieve published notices via expert queries and bulk downloads of notices in XML format for reuse or analysis. This endpoint is openly accessible without authentication.

### Method
POST

### Endpoint
/v3/notices/search

### Parameters
No parameters are documented.

### Request Example
No request example is provided.

### Response
#### Success Response
No response schema is documented.

#### Response Example
No response example is provided.
```

--------------------------------

### POST /v3/notices/submit

Source: https://docs.ted.europa.eu/api/latest/publish.html

Submit new notices for publication in XML format. The notice must have a unique identifier and meet specific requirements, including a valid notice author email and the preferred language for notifications. Upon submission, the notice is validated; if successful, it is marked 'SUBMITTED', otherwise 'VALIDATION_FAILED'.

```APIDOC
## POST /v3/notices/submit

### Description
Submit new notices for publication in XML format. The notice must have a unique identifier and meet specific requirements, including a valid notice author email and the preferred language for notifications. Upon submission, the notice is validated; if successful, it is marked 'SUBMITTED', otherwise 'VALIDATION_FAILED'.

### Method
POST

### Endpoint
/v3/notices/submit

### Parameters
#### Request Body
- **notice** (object) - Required - The notice content in XML format.
- **metadata** (object) - Required - Metadata including noticeAuthorEmail and noticeAuthorLang.
  - **noticeAuthorEmail** (string) - Required - Email of the responsible party.
  - **noticeAuthorLang** (string) - Required - Preferred language for notifications (official EU language).

### Request Example
{
  "notice": "<xml>...</xml>",
  "metadata": {
    "noticeAuthorEmail": "author@example.com",
    "noticeAuthorLang": "en"
  }
}

### Response
#### Success Response (200)
- **businessId** (string) - The unique identifier of the submitted notice.
- **status** (string) - The status of the notice after submission (e.g., SUBMITTED, VALIDATION_FAILED).

#### Response Example
{
  "businessId": "12345",
  "status": "SUBMITTED"
}
```

--------------------------------

### Search API Request: POST /v3/notices/search

Source: https://docs.ted.europa.eu/api/latest/search.html

The Search API request endpoint for searching and retrieving published notices. It is a POST request to /v3/notices/search. Note that business sectors and place of performance are structured hierarchically; consult CPV and NUTS pages for data parsing. The API does not require authentication.

```http
POST /v3/notices/search
```

--------------------------------

### Convert TED XML Notices - API Request

Source: https://docs.ted.europa.eu/api/latest/convert.html

POST request to the Conversion API endpoint to convert a legacy TED XML notice to a draft eForms notice. The response is not shown in the documentation.

```http
POST /v3/notices/convert
Copied!

```

--------------------------------

### Submit Notices for Publication - POST /v3/notices/submit

Source: https://docs.ted.europa.eu/api/latest/publish.html

Use this operation to programmatically submit new notices in XML format for publication. The notice must have a unique identifier, a valid notice author email, and a preferred language that is an official EU language. Upon submission, the notice is validated; if successful it is marked 'SUBMITTED', otherwise 'VALIDATION_FAILED' and cannot be published. Note that in TED API v3, the mandatory property 'noticeAuthorLocale' has been replaced by 'noticeAuthorLang'.

```http
POST /v3/notices/submit
Copied!
```

--------------------------------

### POST /v3/notices/convert

Source: https://docs.ted.europa.eu/api/latest/convert.html

Converts a legacy TED XML notice into a draft eForms notice. This operation is primarily used by eNotices2 but is also available as a stand-alone API for integration and migration purposes.

```APIDOC
## POST /v3/notices/convert

### Description
Converts a legacy TED XML notice into a draft eForms notice. This operation is primarily used by eNotices2 but is also available as a stand-alone API for integration and migration purposes.

### Method
POST

### Endpoint
/v3/notices/convert

### Parameters
No parameters documented.

### Request Example
No request example provided.

### Response
No response details provided.

### Error Handling
No error details provided.
```

--------------------------------

### POST /v3/api-keys/{token}/renew

Source: https://docs.ted.europa.eu/api/latest/developer-operations.html

Automatically renews an API key before it expires, ensuring uninterrupted service without manual intervention. The token is provided in the email notification and can be used to renew keys programmatically.

```APIDOC
## POST /v3/api-keys/{token}/renew

### Description
Automatically renews an API key before it expires, ensuring uninterrupted service without manual intervention. The token is provided in the email notification and can be used to renew keys programmatically.

### Method
POST

### Endpoint
/v3/api-keys/{token}/renew

### Parameters
#### Path Parameters
- **token** (string) - Required - The token sent via email for renewing the API key.

```

--------------------------------

### POST /v3/notices/validate

Source: https://docs.ted.europa.eu/api/latest/validate.html

Validates procurement notices to ensure they meet EU standards by identifying errors and issuing warnings for potential legal issues. This independent service can validate notices anytime before they are sent for publication.

```APIDOC
## [POST] /v3/notices/validate

### Description
Validates procurement notices to ensure they meet EU standards by identifying errors and issuing warnings for potential legal issues. This independent service can validate notices anytime before they are sent for publication.

### Method
POST

### Endpoint
/v3/notices/validate

### Response
#### Success Response (200)
- **validationResult** (object) - The validation result containing errors and warnings.

#### Response Example
{
  "validationResult": {
    "errors": [],
    "warnings": []
  }
}
```

--------------------------------

### Renew API key with POST /v3/api-keys/{token}/renew

Source: https://docs.ted.europa.eu/api/latest/developer-operations.html

Renews an API key before it expires to ensure uninterrupted service. API keys are valid for 24 months and are required to manage unpublished notices. Renewal notifications include a token sent via email, which can be used to manually renew keys or programmatically through the /renew endpoint.

```http
POST /v3/api-keys/{token}/renew
```

--------------------------------

### Stop Publication - POST /v3/notices/{businessId}/stop-publication

Source: https://docs.ted.europa.eu/api/latest/publish.html

Use this operation to stop the publication process for a submitted notice before it is exported to TED. The action is irreversible once the notice reaches the 'publishing' status; it cannot be stopped after that point.

```http
POST /v3/notices/{businessId}/stop-publication
Copied!
```

--------------------------------

### Validate Procurement Notices - POST /v3/notices/validate

Source: https://docs.ted.europa.eu/api/latest/validate.html

Sends a POST request to the Validation API endpoint to validate procurement notices. The service checks notices for errors and warnings, ensuring they meet EU standards before submission for publication. Any notice that passes validation through CVS can be considered technically valid for publication on TED.

```http
POST /v3/notices/validate
Copied!

```

--------------------------------

### POST /v3/notices/{businessId}/stop-publication

Source: https://docs.ted.europa.eu/api/latest/publish.html

Stop the publication process for a submitted notice. This action must be taken before the notice is exported to TED, as the publication process becomes irreversible at that point. Once a notice reaches the 'publishing' status, it cannot be stopped.

```APIDOC
## POST /v3/notices/{businessId}/stop-publication

### Description
Stop the publication process for a submitted notice. This action must be taken before the notice is exported to TED, as the publication process becomes irreversible at that point. Once a notice reaches the 'publishing' status, it cannot be stopped.

### Method
POST

### Endpoint
/v3/notices/{businessId}/stop-publication

### Parameters
#### Path Parameters
- **businessId** (string) - Required - The unique identifier of the notice.

### Response
#### Success Response (200)
- **status** (string) - The new status of the notice after stopping publication.

#### Response Example
{
  "status": "STOPPED"
}
```
Tokens:
Raw