Platform · GeM (Government e-Marketplace)

GeM Tender Data Scraping

The field everyone gets wrong here is consignee location. That is where goods are delivered, and it is often different from where the buying organisation sits. If you filter on the wrong one, you get tenders in the wrong geography.

GeM tender data scraping collects publicly listed bids from India's Government e-Marketplace — bid reference, title, category, quantity, closing datetime, revisions, document links and exemption indicators, with consignee location as a separate field from the buyer.

We collect GeM's public bid listings with both locations as separate fields, plus bid reference, title, category, quantity, closing datetime, revisions, document links and exemption indicators.

Get a free sample See sample data

Free pilot on your own GeM (Government e-Marketplace) list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

gem_bids.jsonl LIVE FEED

{"bid_number":"GEM/2026/B/0000001", "bid_title":"Sample item as listed", "buyer_organisation":"Sample Ministry / Department", "buyer_state":"Delhi","buyer_city":"New Delhi", "consignees":[{"state":"Maharashtra","city":"Pune","quantity":40}, {"state":"Karnataka","city":"Bengaluru","quantity":25}], "bid_end_datetime":"2026-10-28T15:00:00+05:30", "is_ongoing":true, "ongoing_basis":"bid_end_datetime > collected_at", "collected_at":"2026-10-19T09:00:00+05:30", "document_reachable_anonymously":true} {"bid_number":"GEM/2026/B/0000002", "document_url":"https://bidplus.gem.gov.in/...", "document_reachable_anonymously":false, "note":"Document requires a session; URL captured, file not retrieved"} {"bid_number":"GEM/2026/B/0000003", "revision_count":2, "note":"Closing date extended by corrigendum; superseded versions retained"}

3 sample rows, ongoing bids only (illustrative values)consignee separate from buyer · doc reachability flagged · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to GeM (Government e-Marketplace) or its owners. GeM (Government e-Marketplace) and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

GeM (Government e-Marketplace) at a glance

How we handle GeM (Government e-Marketplace) specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Source: Public GeM bid listings
Critical distinction: Consignee location is a separate field from buyer location
Closing time: ISO-8601 with timezone offset
Ongoing filter: Derived by comparing closing datetime with collection time
Documents: URL always; file only where it downloads without a session. Anonymous reachability flagged
Session: None. Anonymous access only
Refresh: Several times daily; hourly near closing windows

Platform specifics

What is specific to GeM

These are the reasons a GeM (Government e-Marketplace) dataset needs its own handling rather than a shared retail schema.

Consignee location is a separate field, and it is the one you filter on

A ministry in Delhi may buy for delivery to several states. Buyer and consignee locations often differ, so we deliver both and recommend filtering on consignees. You can optionally explode the data to one row per consignee, with each exploded row flagged.

Ongoing means a datetime comparison, not a label

Closing times carry timezone offsets, and dates move with extensions and corrigenda. We derive the ongoing flag by comparing bid_end_datetime with collected_at, and we state the basis in ongoing_basis.

Document URLs are public. The documents are not always

Some bid documents download anonymously. Some need a signed-in session, which we do not use. Some sit behind a captcha or a per-document check. We capture the URL every time and flag whether the file was actually reachable.

Scope

What we collect on GeM (Government e-Marketplace), and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

Bid reference, title, category and quantity as listed
Buying organisation with its own state and city
Consignee array, each with state, city and quantity
Optional explode to one row per consignee, flagged as such
Bid end datetime in ISO-8601 with timezone offset
Derived ongoing flag, with the comparison basis stated
Revision count, with superseded versions retained
Document URL, with anonymous reachability flagged
MSE and startup exemption indicators where published

❌ What we do not, and why

Anything requiring a GeM login or seller account
Bid documents behind a session or a per-document verification step
Bidder identities or submitted bids, and award values before the portal publishes them
GeM seller or supplier data, seller lists, or vendor/bidder contact details (phone, email)
Personal data of officials or bidders
Any bid submission, expression of interest or portal interaction

Core GeM (Government e-Marketplace) fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	Meaning
bid_number	The GeM bid reference, the record key
bid_title / category	As listed
quantity / unit	Total quantity and its unit
buyer_organisation / buyer_state / buyer_city	Who is buying, and where they are
consignees	Array of state, city and quantity: the field you filter on
consignee_row	True on exploded rows, so duplication is visible
bid_end_datetime	ISO-8601 with offset. A hard boundary, not a date
is_ongoing / ongoing_basis	Derived, with the comparison stated
revision_count / superseded_by	Corrigenda tracked, originals retained
document_url / document_reachable_anonymously	URL, and whether the file is actually retrievable
collected_at	Observation time, needed to interpret the ongoing flag

Use cases

What teams do with GeM (Government e-Marketplace) data

State-level bid discovery that returns the right tenders

Filter by consignee state and city, so regional teams see bids for delivery in their territory, not just bids from buyers based there.

Ongoing-bid pipelines with a real deadline

Timezone-aware closing times and a stated collection time mean "ongoing" can be trusted in a pipeline.

Category and quantity monitoring

Track demand by category, quantity and consignee state over time.

Document workflow feasibility assessment

Measure what share of documents in your categories are reachable anonymously before you build automation that depends on them.

The 24-hour sample — run on your sources, not ours

Send us your GeM categories, keywords or bid list. We run a real extraction and return it within 24 hours, including the share of documents reachable anonymously.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

Engagement

Three ways to engage us

Managed service (most common)

We handle collection, QA and delivery to your storage or tools. You get a named Actowiz contact on Slack or email.

API access

Authenticated REST endpoints, with sandbox keys for testing.

One-time or project extraction

A fixed-scope extraction delivered once.

Pricing

Quoted individually after a scoping call and a free pilot, then a fixed monthly figure with no per-request metering.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

REST endpoints on the same pipeline, with sandbox keys for testing.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A fixed-scope extraction for a single project or research question.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Pricing is quoted individually, based on category scope, number of markets, cadence and ongoing identity maintenance. After a scoping call and free pilot, we quote a fixed monthly figure, with no per-request metering.

Book a 20-min scoping call Request a quote Talk to an engineer

GeM (Government e-Marketplace) is usually collected alongside its competitors

Most teams pair GeM with CPPP and state e-procurement portals on one schema.

That is what government & tender data covers, and a GeM (Government e-Marketplace)-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

GeM (Government e-Marketplace) data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Buyer and consignee are often in different places. We deliver both, with an optional one-row-per-consignee explode, so you can filter on where goods are delivered.

Yes. We compare the timezone-aware closing datetime with the collection time and state that basis in the record.

We always capture the document URL. We retrieve the file only where it downloads without a signed-in session, and we flag which ones were reachable.

Yes. Revisions are counted and superseded versions are kept.

No. Bidder identities and submitted bids are not public before award. We do not collect personal data, and we do not supply GeM seller or supplier lists or contact details.

It is quoted individually after a scoping call and a free pilot, then billed as a fixed monthly figure.

See real GeM (Government e-Marketplace) data before you commit to anything

Get a free sample on your own categories and a call with an engineer.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner