Keep your sheet. Give it an API.
Let your team work in Google Sheets while applications read a governed JSON contract with authentication, row limits, and usage controls.
| SKU | Product | Price |
|---|---|---|
| SKU-104 | Desk lamp | 45.00 |
| SKU-208 | Notebook | 8.50 |
| SKU-312 | Pen set | 12.00 |
{ "sku": "SKU-104",
"product": "Desk lamp",
"price": 45.00 }- Google Sheets file datasourceWork with the spreadsheet you maintain.
- Private-sheet service-account accessGrant Viewer access to the configured account.
- Trials, limits and marketplace plansPackage data with access and usage controls.
Turn your team’s availability sheet into an API.
Keep team availability in Google Sheets and expose selected fields through an API. Your team edits the rota while consumers use a documented read interface.
From your input to a useful result.
- Choose a sample input
- Apply the feature’s workflow
- Inspect the result
This example runs entirely in your browser with illustrative data. Use the real feature’s guide and listing to check supported inputs, access rules, and pricing.
Explore the example, then use the setup guide to try the real feature.
Project setup and what to check
Input: A supported Sheets URL, a worksheet, and fields such as team, week, and available hours. For a private sheet, grant Viewer access to the configured service account.
Workflow: Connect the source, select the fields and row limits, and test the route. Publish the contract once the returned schema matches what the partner needs.
Result: A read API for a staffing overview or internal capacity lookup. Consumers do not receive spreadsheet editing permissions or a general write-back API.
Test source availability and update behavior. Review mappings before renaming columns or worksheets, because structural changes can break the published contract.
From a familiar sheet to a governed API.
Keep editing in Sheets. Give your applications a consistent integration point.
- 1
Connect your sheet
Use an accessible URL or share private-sheet Viewer access.
- 2
Select your fields
Choose the worksheet, exposed columns, and row limits.
- 3
Test and publish
Verify the JSON contract before offering access.
A familiar sheet. A stable integration point.
Keep data editing in Sheets and give applications a documented read contract.
- Share a private sheet with the configured service-account Viewer.
- Choose the worksheet, exposed fields, and row limits.
- Test the returned schema before publishing your contract.
Example rows and selected JSON fields. The actual response depends on datasource configuration. This is a read workflow, not bidirectional sync.
sku product price
SKU-104 Desk lamp 45.00
SKU-208 Notebook 8.50
SKU-312 Pen set 12.00[
{"sku": "SKU-104", "product": "Desk lamp", "price": 45},
{"sku": "SKU-208", "product": "Notebook", "price": 8.5},
{"sku": "SKU-312", "product": "Pen set", "price": 12}
]Keep your editing workflow
Your team updates the sheet while buyers call the published API.
Choose what to expose
Return selected fields without sharing spreadsheet editing permissions.
A REST API over the spreadsheet your team already maintains
A pricing table, supplier directory, reference list, or research dataset may already live in Google Sheets. Sharing the editing interface is often the wrong integration contract for a partner application. ApiClay's file datasource turns an accessible spreadsheet into an API listing, separating the team's editing workflow from the buyer's programmatic access.
The connection uses supported Google Sheets and Drive export paths. Publishers configure the source URL, worksheet selection, exposed fields, and limits; buyers call the resulting ApiClay contract. This is a spreadsheet-backed read workflow, not a general Google Drive file manager or a promise of bidirectional spreadsheet synchronization.
Connect supported Sheets and Drive export URLs
The file datasource recognizes Google spreadsheet identifiers and uses the appropriate export flow.
How it works
A configured service account can access a sheet shared with it; public-sheet exports are another supported path. A sheet URL alone does not grant permission, so test access with the account and deployment you will use in production.
Choose a deliberate data surface
Worksheet and field settings define the portion of the workbook that becomes a public contract.
How it works
Row limits and trial caps keep exploratory calls bounded. Keep private calculations, internal notes, and unrelated tabs outside the exposed selection, and verify the response rather than assuming spreadsheet formatting controls API access.
Keep the buyer integration independent of file sharing
Buyers use their ApiClay credentials and documented route instead of receiving a Google edit invitation or service-account secret.
How it works
Source values can change through normal spreadsheet editing while the configured route stays the integration point. Renaming a tab or column can still require a configuration update and communication to consumers.
Package spreadsheet data as a product
A Sheets-backed listing uses the same marketplace documentation, plans, trials, reviews, and support surfaces as other datasource APIs.
How it works
Set pricing around the value and access rules of your dataset. For business workflows, combine the published route with a monitor or use it as an input to a batch enrichment job.
Where this fits into your work.
Partner rate cards
Maintain approved prices in a sheet and expose selected fields through a governed route for a partner quote or catalog application.
Curated directories
Keep a reviewed vendor, grant, event, or research directory in a familiar editing tool while selling or sharing structured access.
Approved reference data
Provide applications or AI tools with a controlled table of policy facts, product identifiers, or lookup values without giving them spreadsheet edit permissions.
Start with a focused test.
Use these steps to set up Google Sheets to API and review the result before making it part of a larger workflow.
Connect a Google Sheet →- 1
Prepare access to the sheet
Choose a Google Sheets URL the datasource can read. For a private sheet, share Viewer access with the configured service-account email shown by the publisher flow.
- 2
Map the worksheet and limits
Choose the file datasource in Add API, set the sheet options and exposed fields, and configure row and trial limits. Use consistent column headings and data types.
- 3
Test and publish the JSON contract
Call the route in a private sandbox, confirm the returned fields, and choose trials or paid access. Keep editing the original sheet while buyers use the API listing.
Understand each workflow’s cost.
Match the feature’s limits and billing model to the work you want to run.
Explore API listings →A spreadsheet-backed API follows its listing's trial, subscription, and pay-as-you-go rules. Use the listing's Pricing tab to explain access allowances and row limits to buyers.
Test source availability and update behavior before promising a refresh interval to consumers. A stable route does not make an upstream export continuously available, and structural spreadsheet changes should be treated as potential contract changes.
Open an API listing for its Reference, Playground, and Pricing. Check the selected route’s allowances and applicable infrastructure charges before increasing usage.
FAQs
Does my Google Sheet have to be public?
Not if the deployment has the service-account integration configured and the sheet is shared with that account. Use the configured account email shown by the publisher flow. Merely pasting a private URL does not give ApiClay access.
Can API buyers edit my spreadsheet?
The spreadsheet datasource is intended to expose governed data reads. It does not grant buyers Google editing permissions or provide a general spreadsheet write-back API.
Is this the same as the Excel and CSV connector?
It uses the same file-datasource family but adds Google-specific access and export handling. Use Excel or CSV URLs for hosted file exports and a supported Sheets URL for the spreadsheet workflow.
Can I rename columns after publishing?
You can edit the source, but renamed columns or worksheets may change the contract or break mappings. Review the datasource configuration, re-test, and inform consumers before making a breaking structural change.
Give your spreadsheet a new interface.
Connect a Google Sheet and publish a contract your applications can use.