Turn a Google Sheet
into a read-only API.

Start with a suitable sheet

Use a sheet you are authorized to process. The Google Sheets connector reads a sheet that is already accessible without signing in, through a sharing or published link. Private-sheet Google OAuth is not available.

Give the first row clear, unique column names such as customer_id, company and region. Keep identifiers as text when leading zeros matter. Choose one worksheet for each source.

Connect and check the data

Choose Add data source → Google Sheets. Name the source, paste its link and, when needed, choose the worksheet tab ID from the sheet’s gid parameter.

Choose Check data to inspect the collected schema, field types and sample rows. Select the fields to keep, then connect the checked source. Field choices persist for later refreshes.

Select manual refresh while learning the workflow, or choose a supported schedule when you want Gatherow to collect changes from the same sheet.

Build the table you want to share

Choose Build a table with this source. Pick and rename the output fields in Canvas or Guided steps. Add filters or a sort rule if the finished table needs them.

You can use a single source for this first table. If you add another source, define and check the matching relationship rather than relying on similar-looking row positions.

Review the result and save the table. Your transformations shape the Gatherow output; they do not write changes back to Google Sheets.

Publish the API and choose its access

Open the saved table and start the normal API publishing flow. Choose an endpoint name and path, response columns, default page size and any saved API filters.

Create an API key with access to the endpoint and an appropriate expiry. Copy it privately into the consuming tool. Do not put a live key into a shared spreadsheet, public page or browser-side code.

GET /v1/your-workspace/customer-overview?limit=25
X-API-Key: YOUR_API_KEY

The endpoint documentation in Gatherow contains the actual URL, request example and authenticated preview for your API.

Check the result and its freshness

Confirm that the API returns only the intended columns and rows. Saved endpoint filters always apply; clients can narrow the query further using supported filter and sort parameters.

For more than one page, take meta.snapshot from the first response and pass it as snapshot on later requests. If the table or response settings change, an HTTP 409 response tells the client to restart instead of mixing snapshots.

Check freshness information when the source changes. Collection happens separately from API reads. If a refresh fails, the last valid snapshot remains available rather than triggering a new upstream fetch on every request.

More about the Google Sheets connection