Chronary Connection Setup Links API
The Connection Setup Links API from Chronary — 2 operation(s) for connection setup links.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/chronary-ai:chronary-ai-connection-setup-links-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Chronary Connection Setup Links API
version: 1.0.0
description: 'Calendar-as-a-service API for AI agents.
Manage calendars, events, and availability for AI and human agents.
All endpoints require an API key passed as a Bearer token.
**Authentication:** `Authorization: Bearer chr_sk_...` or `Authorization: Bearer chr_ak_...`
**Rate limit:** 10 requests/second per API key. Exceeds return HTTP 429.
**Quotas:** Monthly operation limits by plan — see Billing & plans and Rate limits.
**Agent bootstrap:** Custom extensions prefixed `x-agent-*` describe the self-signup flow for AI agents. These are not part of any registered OpenAPI extension — they are a Chronary convention.'
contact:
name: Chronary Support
email: support@chronary.ai
url: https://docs.chronary.ai
servers:
- url: https://api.chronary.ai
description: Production
security:
- BearerAuth: []
tags:
- name: Connection Setup Links
paths:
/v1/calendars/{id}/connection-links:
post:
tags:
- Connection Setup Links
description: Create a short-lived URL for a human to connect Google Calendar or Microsoft Outlook. The setup URL secret is returned only once; a reused pending link returns setup_url=null.
parameters:
- schema:
type: string
required: true
name: id
in: path
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
capabilities:
type: array
items:
type: string
enum:
- availability
- publishing
minItems: 1
maxItems: 2
default:
- availability
description: Connection capabilities. "availability" reads free/busy to compute agent availability. "publishing" (writing confirmed Chronary events to the external calendar) is supported for Microsoft Outlook only — Google connections are availability-only and reject the "publishing" capability.
publication_policy:
type: string
enum:
- none
- confirmed
- confirmed_tentative
default: none
responses:
'201':
description: Connection setup link created
content:
application/json:
schema:
$ref: '#/components/schemas/CreatedConnectionLink'
'400':
description: Validation error — invalid request body or query parameters
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
operationId: createConnectionSetupLink
summary: Create connection setup link
x-summary-source: derived
/v1/connection-links/{id}:
get:
tags:
- Connection Setup Links
parameters:
- schema:
type: string
required: true
name: id
in: path
responses:
'200':
description: Connection setup status; never replays the setup secret
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectionLink'
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
operationId: getConnectionSetupLink
summary: Get connection setup link
x-summary-source: derived
delete:
tags:
- Connection Setup Links
parameters:
- schema:
type: string
required: true
name: id
in: path
responses:
'204':
description: Deleted
operationId: deleteConnectionSetupLink
summary: Delete connection setup link
x-summary-source: derived
components:
schemas:
ConnectionLink:
type: object
properties:
id:
type: string
calendar_id:
type: string
status:
type: string
enum:
- awaiting_human
- in_progress
- completed
- declined
- expired
- cancelled
expires_at:
type: string
format: date-time
connection_id:
type:
- string
- 'null'
required:
- id
- calendar_id
- status
- expires_at
Error:
type: object
properties:
error:
type: object
properties:
type:
type: string
example: invalid_request
message:
type: string
example: The field "name" is required.
request_id:
type: string
example: req_01H9X4M2P5R8T6V0
required_plan:
type: string
example: pro
description: 'plan_required: the plan that unlocks the feature'
feature:
type: string
description: 'plan_required: the gated feature'
metric:
type: string
description: 'quota_exceeded and count caps: the metric at its limit (a PLAN_LIMITS key, accepted by POST /v1/billing/upgrade-requests)'
limit:
type: integer
description: 'quota_exceeded and count caps: the plan''s limit for `metric`'
upgrade_url:
type: string
description: Where a human upgrades the plan
docs_url:
type: string
contact_url:
type: string
description: 'Contract-managed plans: where to contact sales'
retry_after:
type: integer
description: Seconds until the request may be retried
required:
- type
- message
- request_id
required:
- error
CreatedConnectionLink:
type: object
properties:
id:
type: string
calendar_id:
type: string
status:
type: string
enum:
- awaiting_human
- in_progress
- completed
- declined
- expired
- cancelled
expires_at:
type: string
format: date-time
setup_url:
type:
- string
- 'null'
format: uri
reused:
type: boolean
required:
- id
- calendar_id
- status
- expires_at
- setup_url
- reused
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: 'API key with `chr_sk_*` for org-level access or `chr_ak_*` for agent-scoped access. Pass in the Authorization header: `Authorization: Bearer chr_sk_...`'
SessionAuth:
type: apiKey
in: cookie
name: chronary_session
description: Console session JWT (HS256), issued by sign-in and sent as the `chronary_session` cookie (a Bearer JWT is also accepted). This is NOT a chr_sk_*/chr_ak_* API key — API keys are rejected with 401 on these endpoints.
x-agent-self-signup:
url: https://api.chronary.ai/v1/agent/sign-up
verify_url: https://api.chronary.ai/v1/agent/verify
restricted_key_returned: true
human_in_the_loop: otp_email
rate_limit: 5 requests per 60s per client IP
x-agent-bootstrap-script:
npx: npx @chronary/agent-init@latest
shell: https://chronary.ai/agent-init.sh
description: One-liner that performs sign-up, prompts for OTP, verifies, and creates a smoke calendar. Accepts CHRONARY_EMAIL and CHRONARY_OTP env vars for non-interactive flows.
x-llms-txt: https://docs.chronary.ai/llms.txt
x-llms-full-txt: https://docs.chronary.ai/llms-full.txt
x-mcp-server-card: https://chronary.ai/.well-known/mcp/server-card.json
x-api-catalog: https://chronary.ai/.well-known/api-catalog