> ## Documentation Index > Fetch the complete documentation index at: https://docs.roark.ai/llms.txt > Use this file to discover all available pages before exploring further. # List what can be booked on a calendar > What an agent can be pointed at on this connection: Cal.com event types today, Google calendars when that lands. Read live from the provider, so an event type added since you connected is here without reconnecting. Each entry carries a `target` ready to put on a calendar tool, so nothing has to assemble one by hand. ## OpenAPI ````yaml /api-reference/openapi.documented.json get /v1/calendar-connection/{connectionId}/targets openapi: 3.1.0 info: title: Roark Analytics API description: >- The Roark Analytics API gives you access to the same API that powers the award winning Roark Analytics platform. version: 1.0.0 servers: - description: Production url: https://api.roark.ai security: - Bearer: [] tags: - name: Agent - name: Agent Endpoint - name: Tool - name: Phone Number - name: Call - name: Chat - name: Metric - name: Metric Policy - name: Metric Collection Job - name: Customer Flow - name: Customer Flow Edge Case - name: Simulation - name: Simulation Persona - name: Simulation Environment - name: Simulation Scenario - name: Simulation Run Plan - name: Simulation Template - name: Simulation Run Plan Job - name: Simulation Job - name: HTTP Request Definition - name: Webhook - name: Issue - name: Autoimprove - name: Agent Config - name: Knowledge Base - name: Calendar Connection - name: Config - name: Organization Project - name: Organization Project Member - name: Organization Project API Key - name: Organization Config - name: CLI Auth - name: Me - name: Project - name: Usage - name: Analytics - name: Dashboard - name: Live Report - name: Benchmark - name: Health - name: Prospect Simulation paths: /v1/calendar-connection/{connectionId}/targets: get: tags: - Calendar Connection summary: List what can be booked on a calendar description: >- What an agent can be pointed at on this connection: Cal.com event types today, Google calendars when that lands. Read live from the provider, so an event type added since you connected is here without reconnecting. Each entry carries a `target` ready to put on a calendar tool, so nothing has to assemble one by hand. operationId: getV1Calendar-connectionByConnectionIdTargets parameters: - name: connectionId in: path required: true schema: type: string description: Calendar connection ID responses: '200': description: What can be booked, as the provider lists it. content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string description: >- Identifier within this connection. Pass it back to read one target in detail. label: type: string description: What the customer called it on the provider. durationMinutes: type: - number - 'null' description: >- How long an appointment runs, when the provider fixes one length. durationOptions: type: array items: type: number description: >- Other lengths this target offers, when it offers a choice. A calendar tool pins one of these with `durationMinutes`; an empty list means the length is not the customer’s to choose. requiresConfirmation: type: boolean description: >- A human has to accept before it is an appointment. An agent booking one of these must say "requested", never "confirmed". isHidden: type: boolean description: >- Hidden on the provider’s own booking page. Still bookable through this API. target: type: object properties: provider: type: string const: CAL_COM eventTypeId: type: integer exclusiveMinimum: 0 required: - provider - eventTypeId title: BookableTargetRef description: >- Ready to put on a calendar tool, so nothing has to assemble one by hand. required: - id - label - durationMinutes - durationOptions - requiresConfirmation - isHidden - target title: BookableTarget description: >- Something on a connected account an agent can be pointed at: a Cal.com event type today, a Google calendar when that lands. required: - data '401': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Authentication error example: type: authentication code: unauthorized message: Authentication required description: Unauthorized '404': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Not found error example: type: not_found code: resource_not_found message: The requested resource could not be found description: Not Found '429': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Rate limit error example: type: rate_limit code: too_many_requests message: Rate limit exceeded description: Too Many Requests '500': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Server error example: type: internal code: internal_error message: Internal server error description: Internal Server Error x-codeSamples: - lang: JavaScript source: >- import Roark from '@roarkanalytics/sdk'; const client = new Roark({ bearerToken: process.env['ROARK_API_BEARER_TOKEN'], // This is the default and can be omitted }); const response = await client.calendarConnection.listTargets('connectionId'); console.log(response.data); - lang: Python source: |- import os from roark_analytics import Roark client = Roark( bearer_token=os.environ.get("ROARK_API_BEARER_TOKEN"), # This is the default and can be omitted ) response = client.calendar_connection.list_targets( "connectionId", ) print(response.data) components: schemas: ErrorResponse: type: object properties: type: type: string enum: - validation - authentication - forbidden - not_found - conflict - payment_required - rate_limit - internal description: The error type category examples: - validation - authentication code: type: string description: Machine-readable error code identifier examples: - invalid_parameter - missing_required_field - unauthorized message: type: string description: Human-readable error message examples: - The request was invalid - Authentication required param: type: string description: The parameter that caused the error (if applicable) examples: - email - user_id details: description: Additional error context information required: - type - code - message securitySchemes: Bearer: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.