Google Calendar

google_calendar · calendar · auth oauth2_auth_code

What you need before your end customers can connect

This connector uses an OAuth grant, so you register one app and all of your end customers connect through it.

Register an app in the provider's developer console.
Add the redirect URL below to that app's allowed callbacks — it must match exactly.
Store the client id and secret with POST /v1/oauth-apps.

Redirect URL to register

https://cloud.ngentix.ai/v1/connect/callback

This exact value goes in the provider app's allowed redirect list. A mismatch is the most common cause of a failed connect.

Scopes we request

https://www.googleapis.com/auth/calendar

Endpoints

Authorization URL	`https://accounts.google.com/o/oauth2/v2/auth`
Token URL	`https://oauth2.googleapis.com/token`
API base	`https://www.googleapis.com/calendar/v3`

Worked example

Connect an end customer, then call the provider on their behalf. Replace cust_123 with your own id for that customer.

curl https://cloud.ngentix.ai/v1/catalog/google_calendar/setup \
  -H "Authorization: Bearer $NGENTIX_API_KEY"

Start a connection for an end customer:

curl -X POST https://cloud.ngentix.ai/v1/connect/sessions \
  -H "Authorization: Bearer $NGENTIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"connector_id": "google_calendar", "consumer_external_id": "cust_123"}'

Then proxy a request through it — X-Ngentix-Consumer is what scopes the call to that end customer:

curl https://cloud.ngentix.ai/v1/proxy/google_calendar/ \
  -H "Authorization: Bearer $NGENTIX_API_KEY" \
  -H "X-Ngentix-Consumer: cust_123"

Machine-readable form of everything above: GET /v1/catalog/google_calendar/setup.