Procore Company Schedule API

The Company Schedule API from Procore — 1 operation(s) for company schedule.

Business capability
Planning & Scheduling BC-5020.30

Operations 1

GET /rest/v1.0/companies/{company_id}/schedule/summary Return company schedule summary #

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/procore:procore-company-schedule-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

procore-company-schedule-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Procore REST Company Schedule API
  version: v1.0/v2.0
  description: Merged from the per-resource OpenAPI documents Procore publishes through its developer portal (https://developers.procore.com/api/v1/resource_groups). Originals are kept verbatim in openapi/_original/resources/.
  x-source: https://developers.procore.com/api/v1/resource_groups
servers:
- url: https://api.procore.com
  description: Production
security:
- bearerAuth: []
tags:
- name: Company Schedule
paths:
  /rest/v1.0/companies/{company_id}/schedule/summary:
    parameters:
    - name: Procore-Company-Id
      in: header
      description: Unique company identifier associated with the Procore User Account.
      required: true
      schema:
        type: integer
    x-compliance-level: partial
    get:
      x-doc:
        visibility: public
        stage: ga
        exposure: public
      summary: Return company schedule summary
      description: Returns per-day counts of schedule tasks and calendar items across company projects for the specified date range. Tasks and calendar items whose start–finish window overlaps the range are included.
      tags:
      - Company Schedule
      parameters:
      - name: company_id
        in: path
        description: Unique identifier for the company.
        required: true
        schema:
          type: integer
      - name: after
        in: query
        description: Start date of the range to summarize (inclusive).
        required: true
        schema:
          type: string
      - name: before
        in: query
        description: End date of the range to summarize (inclusive). Maximum span is 90 days from `after`.
        required: true
        schema:
          type: string
      - name: limit_per_day
        in: query
        description: Maximum number of projects returned per day.
        schema:
          type: integer
          default: 4
      - name: project_ids
        in: query
        description: Filter by project IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_stage_ids
        in: query
        description: Filter by project stage IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_type_ids
        in: query
        description: Filter by project type IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_department_ids
        in: query
        description: Filter by project department IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_office_ids
        in: query
        description: Filter by project office IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_region_ids
        in: query
        description: Filter by project region IDs.
        schema:
          type: array
          items:
            type: integer
      - name: project_owner_type_ids
        in: query
        description: Filter by project owner type IDs.
        schema:
          type: array
          items:
            type: integer
      - name: program_ids
        in: query
        description: Filter by program IDs.
        schema:
          type: array
          items:
            type: integer
      - name: resource_ids
        in: query
        description: Filter tasks by schedule resource IDs.
        schema:
          type: array
          items:
            type: integer
      - name: query
        in: query
        description: Filter projects by name.
        schema:
          type: string
      - name: summary
        in: query
        description: When true, counts only summary tasks.
        schema:
          type: boolean
      - name: milestone
        in: query
        description: When true, counts only milestone tasks.
        schema:
          type: boolean
      - name: project_role_ids
        in: query
        description: Filter by project role IDs.
        schema:
          type: array
          items:
            type: integer
      - name: assignee_ids
        in: query
        description: Filter calendar items by assignee user IDs. When present, task counts are omitted.
        schema:
          type: array
          items:
            type: integer
      - name: milestone_ids
        in: query
        description: Filter by milestone IDs.
        schema:
          type: array
          items:
            type: integer
      - name: sort_key
        in: query
        description: Property used to sort projects within each day. Defaults to descending `project_event_count`.
        schema:
          type: string
          enum:
          - project_event_count
          - project_name
          - estimated_start_date
          - estimated_completion_date
      - name: sort_dir
        in: query
        description: Sort direction for `sort_key`.
        schema:
          type: string
          enum:
          - asc
          - desc
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                description: Per-day company schedule summary across projects.
                properties:
                  data:
                    type: array
                    description: Summary rows, one per day in the requested range that has events.
                    items:
                      type: object
                      properties:
                        date:
                          type: string
                          format: date-time
                          description: Start of the day in UTC for which counts are reported.
                          example: '2023-06-04T00:00:00Z'
                        projects_count:
                          type: integer
                          description: Number of projects with tasks or calendar items on this day.
                          example: 2
                        projects:
                          type: array
                          description: Projects with task or calendar item counts on this day. Size is limited by `limit_per_day`; order follows `sort_key` and `sort_dir`.
                          items:
                            type: object
                            description: Project with counts. `tasks_count` is present only when greater than 0. `calendar_items_count` is present only when greater than 0.
                            properties:
                              id:
                                type: integer
                                description: Unique identifier for the project.
                                example: 1
                              name:
                                type: string
                                description: Display name of the project.
                                example: Project 1
                              tasks_count:
                                type: integer
                                description: Number of schedule tasks on this day.
                                example: 5
                              calendar_items_count:
                                type: integer
                                description: Number of calendar items on this day.
                                example: 3
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    format: int32
                  message:
                    type: string
                  fields:
                    type: string
                  reason:
                    description: A human-readable code providing additional detail on the cause of the error.
                    type: string
                  error:
                    description: Description of the error thrown.
                    type:
                    - string
                    - 'null'
                    example: Invalid Token
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    format: int32
                  message:
                    type: string
                  fields:
                    type: string
                  reason:
                    description: A human-readable code providing additional detail on the cause of the error.
                    type: string
                  error:
                    description: Description of the error thrown.
                    type:
                    - string
                    - 'null'
                    example: Invalid Token
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    format: int32
                  message:
                    type: string
                  fields:
                    type: string
                  reason:
                    description: A human-readable code providing additional detail on the cause of the error.
                    type: string
                  error:
                    description: Description of the error thrown.
                    type:
                    - string
                    - 'null'
                    example: Invalid Token
      x-code-samples:
      - id: node_request
        title: Node.js
        content: "const request = require('request');\n\nconst options = {\n  method: 'GET',\n  url: 'https://api.procore.com/rest/v1.0/companies/%7Bcompany_id%7D/schedule/summary',\n  qs: {\n    after: 'SOME_STRING_VALUE',\n    before: 'SOME_STRING_VALUE',\n    limit_per_day: 'SOME_INTEGER_VALUE',\n    project_ids: 'SOME_ARRAY_VALUE',\n    project_stage_ids: 'SOME_ARRAY_VALUE',\n    project_type_ids: 'SOME_ARRAY_VALUE',\n    project_department_ids: 'SOME_ARRAY_VALUE',\n    project_office_ids: 'SOME_ARRAY_VALUE',\n    project_region_ids: 'SOME_ARRAY_VALUE',\n    project_owner_type_ids: 'SOME_ARRAY_VALUE',\n    program_ids: 'SOME_ARRAY_VALUE',\n    resource_ids: 'SOME_ARRAY_VALUE',\n    query: 'SOME_STRING_VALUE',\n    summary: 'SOME_BOOLEAN_VALUE',\n    milestone: 'SOME_BOOLEAN_VALUE',\n    project_role_ids: 'SOME_ARRAY_VALUE',\n    assignee_ids: 'SOME_ARRAY_VALUE',\n    milestone_ids: 'SOME_ARRAY_VALUE',\n    sort_key: 'SOME_STRING_VALUE',\n    sort_dir: 'SOME_STRING_VALUE'\n  }\n};\n\nrequest(options, function (error, response, body) {\n  if (error) throw new Error(error);\n\n  console.log(body);\n});\n"
      - id: python_python3
        title: Python3
        content: 'import http.client


          conn = http.client.HTTPSConnection("api.procore.com")


          conn.request("GET", "/rest/v1.0/companies/%7Bcompany_id%7D/schedule/summary?after=SOME_STRING_VALUE&before=SOME_STRING_VALUE&limit_per_day=SOME_INTEGER_VALUE&project_ids=SOME_ARRAY_VALUE&project_stage_ids=SOME_ARRAY_VALUE&project_type_ids=SOME_ARRAY_VALUE&project_department_ids=SOME_ARRAY_VALUE&project_office_ids=SOME_ARRAY_VALUE&project_region_ids=SOME_ARRAY_VALUE&project_owner_type_ids=SOME_ARRAY_VALUE&program_ids=SOME_ARRAY_VALUE&resource_ids=SOME_ARRAY_VALUE&query=SOME_STRING_VALUE&summary=SOME_BOOLEAN_VALUE&milestone=SOME_BOOLEAN_VALUE&project_role_ids=SOME_ARRAY_VALUE&assignee_ids=SOME_ARRAY_VALUE&milestone_ids=SOME_ARRAY_VALUE&sort_key=SOME_STRING_VALUE&sort_dir=SOME_STRING_VALUE")


          res = conn.getresponse()

          data = res.read()


          print(data.decode("utf-8"))'
      - id: shell_curl
        title: Curl
        content: "curl --request GET \\\n  --url 'https://api.procore.com/rest/v1.0/companies/%7Bcompany_id%7D/schedule/summary?after=SOME_STRING_VALUE&before=SOME_STRING_VALUE&limit_per_day=SOME_INTEGER_VALUE&project_ids=SOME_ARRAY_VALUE&project_stage_ids=SOME_ARRAY_VALUE&project_type_ids=SOME_ARRAY_VALUE&project_department_ids=SOME_ARRAY_VALUE&project_office_ids=SOME_ARRAY_VALUE&project_region_ids=SOME_ARRAY_VALUE&project_owner_type_ids=SOME_ARRAY_VALUE&program_ids=SOME_ARRAY_VALUE&resource_ids=SOME_ARRAY_VALUE&query=SOME_STRING_VALUE&summary=SOME_BOOLEAN_VALUE&milestone=SOME_BOOLEAN_VALUE&project_role_ids=SOME_ARRAY_VALUE&assignee_ids=SOME_ARRAY_VALUE&milestone_ids=SOME_ARRAY_VALUE&sort_key=SOME_STRING_VALUE&sort_dir=SOME_STRING_VALUE'"
      - id: csharp_httpclient
        title: C#
        content: "var client = new HttpClient();\nvar request = new HttpRequestMessage\n{\n    Method = HttpMethod.Get,\n    RequestUri = new Uri(\"https://api.procore.com/rest/v1.0/companies/%7Bcompany_id%7D/schedule/summary?after=SOME_STRING_VALUE&before=SOME_STRING_VALUE&limit_per_day=SOME_INTEGER_VALUE&project_ids=SOME_ARRAY_VALUE&project_stage_ids=SOME_ARRAY_VALUE&project_type_ids=SOME_ARRAY_VALUE&project_department_ids=SOME_ARRAY_VALUE&project_office_ids=SOME_ARRAY_VALUE&project_region_ids=SOME_ARRAY_VALUE&project_owner_type_ids=SOME_ARRAY_VALUE&program_ids=SOME_ARRAY_VALUE&resource_ids=SOME_ARRAY_VALUE&query=SOME_STRING_VALUE&summary=SOME_BOOLEAN_VALUE&milestone=SOME_BOOLEAN_VALUE&project_role_ids=SOME_ARRAY_VALUE&assignee_ids=SOME_ARRAY_VALUE&milestone_ids=SOME_ARRAY_VALUE&sort_key=SOME_STRING_VALUE&sort_dir=SOME_STRING_VALUE\"),\n};\nusing (var response = await client.SendAsync(request))\n{\n    response.EnsureSuccessStatusCode();\n    var body = await response.Content.ReadAsStringAsync();\n    Console.WriteLine(body);\n}"
      x-rate-limit-enabled: true
      x-procore-kong-tags:
      - rate-limit:enabled
      x-changelog:
      - summary: New 'Show summary' API version
        description: Tallies tasks and calendar items for a given company.
        endpoint: GET /companies/{company_id}/schedule/summary
        type: new
        breaking: false
        datestamp: '2023-07-24'
        versions:
        - '1.0'
        x-doc:
          visibility: public
          stage: ga
          exposure: public
        link: company-schedule?version=1.0#return-company-schedule-summary
      operationId: returnCompanyScheduleSummary
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer