The complete GKit guide for developers

GKit for developers, in one page

GKit is a suite of Google Workspace tools that share a single Google account. This guide covers what you need to integrate with it.

Authentication

GKit uses Google OAuth via Auth.js. Sign in once at gkit.mreshank.com and a secure session is set on the .gkit.mreshank.com domain — shared across every product subdomain, so you never log in twice.

For programmatic access, each product issues its own API keys scoped to your account. See the authentication docs.

The SheetsAPI REST interface

GET    /api/spreadsheets/{userKey}/{sheet}         # list rows
GET    /api/spreadsheets/{userKey}/{sheet}/{row}   # single row (1-based)
POST   /api/spreadsheets/{userKey}/{sheet}         # create row(s)
PUT    /api/spreadsheets/{userKey}/{sheet}/{row}   # update
DELETE /api/spreadsheets/{userKey}/{sheet}/{row}   # delete

Responses are JSON. The first row of each sheet tab defines the field names. Search, sort, field projection, pagination, and alternate formats (CSV/TSV/XML/JSONP) are supported via query parameters — see the REST API reference.

Limits

While in beta there's no per-key request throttle. The list endpoint caps limit at 1000 rows (use offset to paginate), and requests are still subject to Google's own Sheets API quotas. The worker runs on Cloudflare's edge, so latency is low worldwide. See limits & fair use.

One account, many products

Because every product shares the same session and account model (GKitUser), building a second integration is trivial — the auth you set up for SheetsAPI carries over to every future GKit product.

Start with the quickstart.