GET /rest/v2.0/companies/{company_id}/projects/{project_id}/schedules/{schedule_id}/activity_links
List all activity links in a schedule
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
String | Yes |
Unique identifier for the project |
schedule_id |
String | Yes |
Unique identifier for the schedule |
company_id |
String | Yes |
Unique identifier for the company |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Procore-Company-Id |
Integer | Yes |
Unique company identifier associated with the Procore User Account. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
page |
Integer | No |
The page number to retrieve |
filters[id] |
String | No |
Filter activity links by ID |
sort |
String | No |
Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending Valid values:
|
per_page |
Integer | No |
Number of records per page Default value: 10 |
filters[from_activity] |
String | No |
Filter activity links by predecessor activity IDs (bracket list syntax like [1,2]) |
filters[to_activity] |
String | No |
Filter activity links by successor activity IDs (bracket list syntax like [1,2]) |
filters[updated_at][gt] |
String | No |
Filter for activity links updated after this timestamp (ISO 8601) |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.