Tender data API · read-only

Find the tender on day one. Not four days before it closes.

Notices, lots, documents and award results from Portal de Compras Publicas, Etimad, DIBBS, Dubai eSupply and five more portals, returned as JSON. Built for bid and capture managers who are done opening six portals by hand every morning.

17 endpoints · 9 portals · 6 jurisdictions · public data only, no bid submission
RADAR / SAMPLE PIPELINE--:--:-- UTC
7d14d28d
Keyword profile
0matching notices
0closing in under 5 days
Closer to the centre = closer to the deadline. Orange = matches the profile.
Simulated data for illustration. Tenders, buyers, values and deadlines are invented, not real notices.
17endpoints you can call today
9procurement and funding portals
6jurisdictions: Brazil, Saudi Arabia, UAE, United States, Canada, EU
6/17on Portal de Compras Publicas alone, from notice to award to chat log
01 You already know this

The tender was public for three weeks. You saw it on day seventeen.

MON 07:40 / BEFORE THE STAND-UP

Six portals, six logins, six search forms

Portuguese on one, Arabic on the next, an NSN search on a third. Someone on your team does this by hand every morning, and nobody does it the week they are on leave.

Portal 1 / search "luvas"checked
Portal 2 / session expiredretry
Portal 3 / new CAPTCHAretry
Portal 4 / municipalskipped
Portal 5 / Gulfskipped
Portal 6no time
THU 16:10 / FORWARDED BY SALES

"Is this one for us?" Yes. It closes Monday.

A perfect-fit lot, found four days before the deadline. No time for the site visit, the clarification questions or the supplier quotes. You log it as no-bid and move on.

Notice publishedday 0
Clarifications closeday 12
You found itday 17
Deadlineday 21
Decisionno-bid
TOO LATE
NEXT YEAR / SAME BUYER, SAME LOT

Who won last time, and at what unit price?

The aggregator you pay covers federal notices and stops there. The municipal award, the homologated item prices and the chat log from the session were public. Nobody on your side saved them.

Last award, winnerunknown
Winning unit priceunknown
Number of biddersunknown
Your price this yeara guess
02 Coverage

Municipal Brazil, the Gulf and DLA. The portals the federal aggregators leave out.

This is the full inventory today: 17 endpoints across 9 portals. Each one is a hosted function with a stable ID that returns JSON.

GSA eLibrary and the EC state aid register are reference data (schedule holders, grant awards), not open tender lists. Need a portal that is not here? Ask - see the FAQ.
03 The API

One POST per portal query. JSON back.

01

Pick an endpoint. List tenders on Portal de Compras Publicas, award results on Etimad, open RFQs on DIBBS. Each is a function ID.

02

Call it with your variables. We open the portal in a real browser on our side, run the search and read the public page. You get structured JSON instead of a search form.

03

Schedule your own polling. This is a request API: data is read from the portal at call time. It is not a push stream. Run it from cron each morning, diff against yesterday, alert on new matches.

04

Keep the awards. Pull homologated items and award results after closing and store winner and price next to the notice, ready for the next round.


    
04 Try it

Your keywords against a sample pipeline. What could you still bid on?

Type what you sell. Set how many days your team needs to prepare a compliant bid. The watchlist shows which sample tenders match, how long is left, and which ones are already lost to late discovery.

Enter or comma adds a keyword. Backspace removes the last.
10 days
notice window already elapsedyour preparation timetodaySimulated sample of 15 invented tenders. Not live portal data.
05 From the bid desk

What changes when the morning portal round is a cron job.

Placeholder review

"I used to open the municipal portal, search five terms, and paste rows into a spreadsheet before my first coffee. Now a script does the round and I get one list of new notices with the deadline next to each. I spend the morning reading the edital instead of hunting for it."

RM
Renata M.Bid manager, medical supplies distributor, 40 staff
Placeholder review

"The award results were what sold me. We pull who won and at what price after every tender we watched, even the ones we skipped. Pricing the next round is no longer a guess."

KA
Khalid A.Capture manager, facilities contractor
Placeholder review

"We run a tender-alert product. Building and babysitting a scraper per portal was eating the roadmap. We call the endpoints on our own schedule and put our effort into matching."

DP
Dana P.Product lead, tender-alert startup
06 Pricing

Priced per call. Less than the hours your team spends on the morning round.

Scout
$0
Check the coverage against your own keywords.
  • 250 calls a month
  • All 17 endpoints
  • No card required
Get a key
Bid desk
$249 /mo
For a supplier watching several portals every day.
  • 10,000 calls a month
  • All 17 endpoints, all 9 portals
  • Documents and award endpoints included
  • Email support
Start a 14-day trial
Platform
Custom
For tender-alert products and larger capture teams.
  • Volume pricing
  • New portals scoped on request
  • Private endpoints
  • Shared channel with the team
Talk to us
Sizing example: 5 list endpoints polled every 2 hours, every day = 5 x 12 x 30 = 1,800 calls a month, plus one detail call per new match you open.
07 FAQ

Questions a careful bid manager asks.

How fresh is the data? Do you push new tenders to me?

Each call reads the portal at request time, so you get what the portal shows at that moment. It is a request API, not a push stream and not a pre-built database. You schedule the polling, for example every morning or every few hours, and compare against your last result to spot new notices.

Does Bidfeed submit bids or register us as a supplier?

No. It is read-only public tender data. It does not submit bids, upload proposals, send clarification questions or act inside a supplier account. Your team still decides and bids through the portal.

Which portals and what exactly is covered?

The 17 endpoints listed in the coverage section, across 9 portals in 6 jurisdictions. Depth varies: Portal de Compras Publicas has six endpoints from notice to awarded items and chat logs, while DIBBS has one open RFQ search. We do not list anything we do not have.

What language is the data in?

Fields come back as the portal publishes them, so a Brazilian municipal notice is in Portuguese. Keys in the JSON are in English. Match with keywords in the portal's language, or translate on your side.

Can I get the tender documents?

Portal de Compras Publicas has a tender documents endpoint that returns the documents the portal publishes for a tender. For other portals, the details endpoints return what the public notice page shows.

Can you add a portal we need?

Ask. Endpoints are hosted functions built against a specific portal, so a new one is scoped case by case. We will tell you plainly if a portal is not feasible.

What happens when a portal changes its site?

The function is repaired on our side and keeps its ID, so your integration should not need to change. Build your poller to tolerate an occasional failed run and retry.

Who runs this?

Bidfeed is built on Notte, a platform for running browser automations as hosted functions. Bidfeed is not affiliated with any government body or with the portals named on this page.

The next tender in your category is already published somewhere.

Put the morning portal round on a schedule and spend the time on the bid.