Skip to main content
The Data API is the backbone of your Google workspace, giving you structured access to every record your team creates and manages. From simple documents to richly tagged, field-rich entries, you can query across your entire dataset with powerful filters, sort results by any field, and perform bulk operations to keep large collections in sync. All endpoints are authenticated via Bearer token and return JSON.

List Records

Retrieve a filtered, sorted, and paginated list of records from your workspace. GET https://api.google.com/v1/data

Query Parameters

string
Filter records by type (e.g., document, task, note).
string
Filter by record status. Common values: active, archived, draft.
integer
Page number to retrieve. Defaults to 1.
integer
default:20
Number of records to return per page. Defaults to 20. Maximum is 100.
string
Field name to sort results by. Common values: created_at, updated_at, name.
string
Sort direction. Accepted values: asc, desc. Defaults to asc.
string
Full-text search query. Searches across record names and field values.

Example Request

Example Response


Get Record

Fetch a single record by its unique ID, including all fields and tags. GET https://api.google.com/v1/data/:id

Path Parameters

string
required
The unique identifier of the record to retrieve (e.g., rec_abc123).

Example Request

Example Response


Create Record

Add a new record to your workspace. You can include custom key-value fields and any number of tags to keep records organized. POST https://api.google.com/v1/data

Body Parameters

string
required
A human-readable name for the record.
string
required
The record type (e.g., document, task, note). Used for filtering and categorization.
object
An optional object of custom key-value pairs to attach to the record. Values must be strings.
array
An optional array of string tags for labeling and grouping records.

Example Request

Example Response

Use consistent type values across your workspace to make filtering and reporting more effective. Consider establishing a naming convention for your team before you start creating records at scale.

Update Record

Apply partial updates to an existing record. You only need to include the fields you want to change — any omitted fields retain their current values. PATCH https://api.google.com/v1/data/:id

Path Parameters

string
required
The unique identifier of the record to update.

Body Parameters

string
Updated name for the record.
object
Updated custom fields. Provided keys are merged with existing fields; existing keys not mentioned are preserved.
array
Updated tags array. This fully replaces the existing tags list.
string
Updated status for the record (e.g., active, archived, draft).

Example Request

Example Response


Delete Record

Permanently delete a single record from your workspace. DELETE https://api.google.com/v1/data/:id
Record deletion is permanent and cannot be undone. All fields, tags, and associated metadata are immediately removed. If you want to retain the data but remove it from active views, consider setting status to archived via the Update Record endpoint instead.

Path Parameters

string
required
The unique identifier of the record to delete.

Example Request

A successful deletion returns HTTP 204 No Content with an empty body.

Bulk Operations

When you need to create or delete many records at once, bulk endpoints let you perform those operations in a single API call rather than looping through individual requests.

Bulk Create

Create multiple records in one request by sending an array of record objects. The response contains an array of the newly created records in the same order. POST https://api.google.com/v1/data/bulk-create

Example Request

Example Response

Bulk Delete

Delete multiple records in one request by providing an array of record IDs. DELETE https://api.google.com/v1/data/bulk-delete
Bulk deletion is permanent. All specified records and their associated data will be immediately and irreversibly removed.

Example Request

Example Response


Error Reference

The request body is missing required fields (name or type) or contains invalid values. Check the request structure and try again.
Your API key is missing or invalid. Ensure you include a valid Bearer token in the Authorization header.
No record exists with the specified id. Verify the ID is correct.
The request is well-formed but contains semantic errors, such as unrecognized field types or empty required values.
You have exceeded the API rate limit. Wait before retrying. Check the Retry-After response header for the cooldown period.