Exports and a Google Sheets copy now; a public API is not part of version 1
If you are checking survey app API integration before you buy, here is the straight answer. Bharat Survey version 1 gets data out through exports in CSV, Excel and PDF, and a one-way copy into Google Sheets. It does not yet offer a public REST API or webhooks. This page shows what each route delivers, how analysts move data into SPSS, Stata or R, and how to plan around the gap.
What is available, what is not, and what to use instead.
| Route | Status | Use it for |
|---|---|---|
| CSV export | Available | Analysis tools, data warehouses, archiving |
| Excel export | Available | Managers, quick review, sharing |
| PDF export | Available | Reports, case files, sign-off |
| Google Sheets one-way copy | Available | Live-ish shared sheets for teams |
| Public REST API | Not in v1 | Plan on exports or Sheets for now |
| Webhooks on new records | Not in v1 | Scheduled exports instead |
| Direct SPSS .sav file | Not in v1 | CSV plus codebook into SPSS |
If an API or webhook is essential for your project, say so at the start. We will tell you plainly whether we can meet it and when.
Each format has a job. Pick by who opens the file next.
A workbook with one sheet for main records and separate sheets for repeat groups such as household members, linked by record ID. Opens directly for filters and pivots.
Plain comma-separated files with stable column names taken from the form's question names. Suitable for loading into statistical software, databases or a data warehouse.
Formatted reports of individual records or summaries, for case files, government submissions and sign-off where a printed document is still expected.
SPSS, Stata and R all start from the CSV. There is no native .sav export, but the route is short when the form was built well.
The Sheets copy pushes records one way from Bharat Survey into a Google Sheet your team controls. It suits dashboards built in Sheets or Looker Studio, and teams who already review numbers there. Edits made in the Sheet do not flow back into Bharat Survey, which keeps the source of truth in one place.
Teams that would use a webhook to trigger a follow-up, such as a callback or a ticket, can often work from the Sheets copy with their own automation on the Sheet, or from scheduled exports. It is not as immediate as a webhook, and we will not pretend it is.
Exports include latitude, longitude, accuracy, location state, timestamps, duration and form version, so verification evidence travels with the data into whatever system receives it.
Most survey and evaluation projects
Operational integrations
All platform capabilities.
Learn moreProject-specific work on top of the core app.
Learn moreFeedback programmes and their exports.
Learn moreInspection results in Excel and PDF.
Learn moreMessaging channels and their limits.
Learn moreStraight answers to the questions people ask most about this topic.
Not a public one in version 1. Data leaves the platform through CSV, Excel and PDF exports and a one-way copy to Google Sheets. If an API is essential for your project, tell us at the start and we will be clear about whether and when it can be met.
Yes, through CSV. Export the CSV, then apply variable and value labels from the form's question names and choice lists. There is no direct .sav export, but a well-built form makes the labelling a one-time script per form version.
As separate tables. The main record sits in one file or sheet, and each repeat group, such as household members, sits in another with the parent record ID, so they can be joined in any analysis tool.
No. The Sheets copy is one way. Changes in the Sheet stay in the Sheet. Corrections to records are made in Bharat Survey through the review process, so the audit trail stays intact.
Tell us the system, the fields and how quickly data must arrive. We will tell you honestly what works today.
