Home » API Documentation

Tenders API Documentation

Overview:

The TendersOnTime API is a REST-based service that allows users to retrieve tender data strictly based on the tender posting date.

This API is designed for daily data synchronization. Users are expected to pull tender data for a specific posting date, store it in their own database, and apply any additional filters or business logic within their own application.

All keywords, regions, and classification filters are pre-configured and managed at the TendersOnTime backend based on mutually finalized requirements.


Base URL:
https://tmproject.tendersontime.org/tmpApi/tender-pull-json-tot.php


Authentication:

Authentication is mandatory for all requests.

username (required): Your API username.

key (required): Your API key for authentication.


Endpoints:

  1. Retrieve Tenders by Date
  2. Retrieve all tenders posted on a specific date.

    • Method: GET
    • Endpoint: /tender-pull-json-tot.php
    • Parameters:
    •  Request Fields   Field type   Field Description 
      usernamestringrequired, Your API username.
      keystringrequired, Your API key for authentication.
      datestringrequired, Date of posting in YYYY-MM-DD format.

      The API does not accept any additional filters apart from the date parameter.

      Keyword, region, and category filtering is handled internally at the backend.

    • Success Response:
      • Status: 200 OK
      • Content-Type: application/json
      • Body:
      • JSON
        {
          "status": "success",
          "message": "tender success",
          "posting_date": "YYYY-MM-DD",
          "total": 00,
          "data": [
            {
              // Tender data object
            }
          ]
        }
        

    • Error Response:
      • Status: 400 Bad Request
      • Content-Type: application/json
      • Body:
      • JSON
        {
          "status": "error",
          "message": "Error Message",
          "data": []
        }
        


Sample Request:

GET
https://tmproject.tendersontime.org/tmpApi/tender-pull-json-tot.php?username=tot&key=sd5dsg6s4gj5y&date=2024-01-18
  Copy

Sample Response:

JSON
{
  "status": "success",
  "message": "tender success",
  "posting_date": "2024-01-18",
  "total": 20,
  "data": [
    {
      // Tender data object
    },
    {
      // Tender data object
    },
    ...
  ]
}

Recommended Data Synchronization Strategy

To ensure timely and complete tender data coverage, we recommend the following synchronization approach:

  • Newly published tenders are synchronized to the API backend at a maximum interval of every 3 hours. To keep your system up to date, you may pull current-day tender data every 3 hours using the current posting date.
  • This periodic pull ensures that any tenders published throughout the day are captured in near real-time within your system.
  • On the following day, we strongly recommend performing one final pull for the previous day’s posting date. This ensures that all tenders published on that day—including any late updates—are fully retrieved and stored in your database.

Notes:

  • Ensure to use valid credentials (username and key) for authentication.
  • Handle error responses gracefully by checking the status and message fields in the response.
  • In the provided Sample API endpoint for fetching tender data is not based on date parameter in this API documentation.

Frequently Asked Questions (FAQs)

Q1. How up-to-date is the tender information?

Our system continuously updates tender postings throughout the day, so you can access the latest tenders in near real-time.

Q2. How quickly can we start using the API?

The API is designed for easy and fast integration, allowing you to pull tender data into your system a few days, depending on your setup.

Q3. What filters are supported by the TendersOnTime API?

The API supports only one request-level filter: the tender posting date (date).
Other filters such as keywords, regions, categories, or organizations are not accepted as API parameters. These filters are pre-configured and managed at the backend based on mutually finalized requirements.

Q4. How frequently should we call the API?

Newly published tenders are synchronized to the API backend every 3 hours.
For up-to-date data, you may pull current-day tenders every 3 hours.
Additionally, it is recommended to pull the previous day’s data once on the next day to ensure all tenders published on that date are fully captured.

Q5. Do we need unlimited API hits during the trial or production usage?

No. Unlimited API hits are not required.
Following the recommended synchronization strategy (periodic pulls for the current day and a final pull for the previous day) is sufficient to retrieve all relevant tender data efficiently.

Q6. Can we apply our own filters such as keywords or regions?

Yes, but only after retrieving the data.
API Users are expected to store the API response in their own database and apply any additional filters, analytics, or business logic within their application layer.

Q7. What happens if we miss pulling data for a specific day?

If a daily pull is missed, you can still retrieve the data by calling the API with the relevant posting date, as long as the data is active/live.
However, we strongly recommend regular scheduled pulls to avoid gaps and ensure data completeness.

Call Action

Get A Callback Within 24 Hours

Fill form below to get callback from Tender Experts.

Captcha

Click button to send your details.