Google: Creates a secondary calendar The authenticated user for the request is made the data owner of the new calendar Note: We recommend to authenticate as the intended data owner of the calendar You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user Don't use a service account for authentication If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior For example, if a service account is the data owner, data ownership cannot be transferred
Google calendarCalendars.calendarCalendarsInsert: arguments, response, policy and SDK examples.
← calendar_calendars operations · Get started · OpenAPI downloads
Contract 2026-10-27 · Operation google.calendar_calendars_insert
Provider route: POST /calendar/v3/calendars. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/google with npm, or alter-sdk-google with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { GoogleIntegration } from "@alter-ai/google";
async function execute(input: Parameters<GoogleIntegration["calendarCalendars"]["calendarCalendarsInsert"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new GoogleIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.calendarCalendars.calendarCalendarsInsert(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_google import GoogleIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = GoogleIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.calendar_calendars.calendar_calendars_insert(arguments) result = await call.wait() return result.body_json()Referenced models: Creates a secondary calendar.
The authenticated user for the request is made the data owner of the new calendar.
Note: We recommend to authenticate as the intended data owner of the calendar You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user Don’t use a service account for authentication If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior For example, if a service account is the data owner, data ownership cannot be transferred — request body — body, Returns a single user setting — request body — query
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Returns metadata for a calendar — response body |
Referenced models: Returns metadata for a calendar — response body
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: google.calendar_calendars_insert. Catalog operation: calendar.calendars.insert. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["https://www.googleapis.com/auth/calendar", "https://www.googleapis.com/auth/calendar.app.created", "https://www.googleapis.com/auth/calendar.calendars"]