Posit Schedules API
The Schedules API from Posit — 1 operation(s) for schedules.
The Schedules API from Posit — 1 operation(s) for schedules.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/posit:posit-schedules-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
contact:
email: support@posit.co
name: Posit Connect Support
url: https://support.posit.co/hc/en-us
description: '## Overview
The Posit Connect Server API can be used to perform certain
user actions remotely.'
license:
name: Commercial. Copyright 2015-2026 Posit Software, PBC. All Rights Reserved.
url: https://posit.co/about/eula/
termsOfService: https://posit.co/about/eula/
title: Posit Connect API Reference Schedules API
version: 1.0.1
servers:
- url: /__api__
security:
- apiKey: []
tags:
- name: Schedules
paths:
/v1/content/{guid}/schedule/history:
get:
description: 'Get the schedule change history for a piece of content.
Returns the current schedule (if any) and a list of historical changes
including when schedules were created, updated, or deleted.
Schedule data is returned in RFC 5545 (iCalendar) format.
A maximum of 100 history entries are returned, ordered by change time
(most recent first).
This action is permitted for content owners, users with collaborator
or editor rights, and administrators.'
operationId: getScheduleHistory
parameters:
- in: path
name: guid
required: true
schema:
format: uuid
type: string
- in: query
name: variant
schema:
type: string
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduleHistoryResponse'
description: Successful response.
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
description: The requested operation is invalid.
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
description: The requested operation requires authentication.
'403':
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
description: You do not have permission to perform this operation.
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
description: The requested object does not exist.
'500':
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
description: A server error occurred.
summary: Get schedule history
tags:
- Schedules
components:
schemas:
VariantScheduleHistory:
additionalProperties: false
properties:
variant_key:
description: The unique key identifying this variant.
example: HidI2Kwq
type: string
current_schedule:
allOf:
- $ref: '#/components/schemas/CurrentSchedule'
description: 'The current active schedule for this variant, or null if no
schedule exists.'
history:
description: 'A list of schedule change history entries, ordered by change time
(most recent first). Limited to the 100 most recent entries.'
items:
$ref: '#/components/schemas/ScheduleHistoryEntry'
type: array
total_count:
description: 'The total number of history entries for this variant. This may be
larger than the number of entries in the `history` array, which is
limited to 100 entries.'
example: 3
type: integer
type: object
User:
description: A user object.
properties:
email:
description: The user's email.
example: jon.doe@example.com
type: string
username:
description: The user's username.
example: jondoe
type: string
first_name:
description: The user's first name.
example: Jon
type: string
last_name:
description: The user's last name.
example: Doe
type: string
user_role:
description: The user's role.
enum:
- administrator
- publisher
- viewer
example: administrator
type: string
created_time:
description: 'The timestamp (RFC3339) indicating when the user was created in
the Posit Connect server.'
example: '2006-01-02T15:04:05-07:00'
format: date-time
type: string
updated_time:
description: 'The timestamp (RFC3339) indicating when information about this
user was last updated in the Posit Connect server.'
example: '2006-01-02T15:04:05-07:00'
format: date-time
type: string
active_time:
description: 'The timestamp (RFC3339) indicating approximately when the user
was last active. Highly active users only receive periodic updates.'
example: '2006-01-02T15:04:05-07:00'
format: date-time
type:
- string
- 'null'
confirmed:
description: 'When `false`, the created user must confirm their account through
an email. This feature is unique to password authentication.'
example: true
type: boolean
locked:
description: Whether or not the user is locked.
example: false
type: boolean
external_id:
description: 'The unique identifier for this user from the authentication
provider, when available.'
example: okta-12345-abcde
type: string
guid:
description: 'The user''s GUID, or unique identifier, in UUID
[RFC4122](https://www.rfc-editor.org/rfc/rfc4122)
format'
example: 6f300623-1e0c-48e6-a473-ddf630c0c0c3
format: uuid
type: string
type: object
APIError:
additionalProperties: false
description: The error object returned by the API on failure.
properties:
code:
description: The specific code for the type of error returned. See the [API error codes reference](#api-error-codes) for the full set of values.
type: integer
error:
description: A description of the problem that was encountered.
type: string
payload:
description: Additional error details, if any. The structure varies by error type.
type:
- object
- 'null'
required:
- code
- error
type: object
HistorySchedule:
additionalProperties: false
properties:
schedule:
allOf:
- $ref: '#/components/schemas/RRuleSet'
description: The schedule definition in RFC 5545 (iCalendar) format.
type: object
ScheduleHistoryEntry:
additionalProperties: false
properties:
change_type:
description: The type of change that was made to the schedule.
example: updated
type: string
change_time:
description: The timestamp (RFC3339) when this change was made.
example: '2025-01-15T14:30:00Z'
format: date-time
type: string
user:
allOf:
- $ref: '#/components/schemas/User'
description: The user who made this change, or null if the user has been deleted.
new_schedule:
allOf:
- $ref: '#/components/schemas/HistorySchedule'
description: 'The schedule state after this change, or null if the schedule
was deleted.'
type: object
RRuleSet:
additionalProperties: false
description: RFC 5545 recurrence rule components for a schedule.
properties:
dtstart:
description: 'The DTSTART component specifying when the schedule begins,
including timezone information.'
example: DTSTART;TZID=America/New_York:20240115T090000
type: string
rrules:
description: An array of RRULE components defining the recurrence pattern.
example:
- RRULE:FREQ=DAILY;INTERVAL=2
items:
type: string
type: array
until:
description: The UNTIL component specifying when the schedule ends, if applicable.
example: UNTIL=20240215T090000Z
type: string
type: object
ScheduleHistoryResponse:
additionalProperties: false
properties:
results:
description: An array of schedule history results, one per variant.
items:
$ref: '#/components/schemas/VariantScheduleHistory'
type: array
type: object
CurrentSchedule:
additionalProperties: false
properties:
schedule:
allOf:
- $ref: '#/components/schemas/RRuleSet'
description: The schedule definition in RFC 5545 (iCalendar) format.
next_run:
description: 'The next scheduled run time (RFC3339), or null if no future
run is scheduled.'
example: '2024-01-17T14:00:00Z'
format: date-time
type:
- string
- 'null'
type: object
securitySchemes:
apiKey:
description: 'Prefix your API key with `Key `, e.g. `Key ABC123`.
'
in: header
name: Authorization
type: apiKey