--- title: "Activities" slug: "safran-project-integration-api-activities" updated: 2026-09-23T10:45:48Z published: 2026-09-23T10:46:37Z canonical: "docs.safran.com/safran-project-integration-api-activities" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.safran.com/llms.txt > Use this file to discover all available pages before exploring further. # Activities ## Activities ### /v1/activities List Of Activities ### Example for calling: http://server/v1/activities/1 - retrieves all activities for the network with network id = 1 http://server/v1/activities?network_id=1 – retrieves all activities in the network having id = 1 http://server/v1/activities?network_id=1&subnetwork_id=2 – retrieves all activities in network having id = 1 and subnet id = 2 http://server/v1/activities?id=1 – retrieves all activities having id = 1 http://server/v1/activities - will produce "400 - Bad Request" as the list of activities could be very large. http://server/v1/activities?network_id=1&subnetwork_id=205&uf_flag21=false&uf_date10=2022-01-04T07:28:00.000&uf_ref4=DG4¤t_progress=100.0 – retrieves all activities in network matching all given request fields. http://server/v1/activities?network_id=1&Unsupported=1 - will produce "200 - OK" with an empty result, as the API does not recognise the Unsupported as a request field. http://server/v1/activities?network_id=1&meta_field_select=id - retrieves all activities in project 1 but lists only the network_id and id fields. http://server/v1/activities?network_id=1&cancelled=null - retrieves all activities in project 1 which has not been cancelled. http://server/v1/activities?network_id=1&uf_out2=C2.1§C2.2 - retrieves activities with outline code 2 linked to structure with "C2.2" and its parent "C2.1". Request Body = {….} see request fields below ### Allowed Methods: [GET] API Controller: **activities** ### Description: Lists activities for the supplied network_id, sorted by activity id. Though stored in the activities table as sequences, Reference and Outline code user fields are resolved to their actual field values. ### Request Fields: | Name | Type | Description | Notes | | --- | --- | --- | --- | | network_id | integer | Network Id | [Optional] Returns all activities if none specified | | id | integer | Activity Id | [Optional] Returns activities with seq = ID. | | owner | string | Networks owner | [Optional] Relates to "**SafranWebAPIOwnerVerificationDuringApiCalls**" in [Application Settings](/v1/docs/safran-project-integration-api-application-settings) | | item_guid | guid | Activity guid | [Optional] Returns activity with given guid | | subnetwork_id | integer | The Sub network id the activity belongs within. | [Optional] Returns all activities if none specified, requires network_id. | | meta_field_exclude | string | Comma separated list of field names to exclude in the response object(s) | [Optional] All fields are returned if not specified. | | meta_field_select | string | Comma separated list of field names to include in response object(s) | [Optional] All fields are returned if not specified, else only *the fields listed will be included in the return result.* some fields are mandatory and will be included regardless. | | ~~meta_include_resources~~ | integer | Specifies whether to include resources assigned to activity in response. | [Optional] Will not return resources if not specified, unsupported at the moment. | | ~~meta_limit~~ | integer | A limit on the number of activities to be returned by this call | [Optional] Will return all network activities if no limit specified, unsupported at the moment. | | meta_ending_at | integer | Activity Id for selecting the activity range prior. Could be used for breaking down retrieval into multiple calls (pagination, for example) | [Optional]Example: If a project has activity id’s 1 - 1000, and the call is made with **meta_ending_at** = 500, activities 1-500 would be selected. | | meta_starting_after | integer | Activity Id for selecting the activity range after. Could be used for breaking down retrieval into multiple calls (pagination, for example) | [Optional]Example: If a project has activity id’s 1 - 1000, and the call is made with **meta_starting_after** = 500, activities 501-1000 would be selected. | | meta_ending_at_row | integer | Row Number selecting activity range prior. Could be used for breaking down retrieval into multiple calls (pagination, for example) | [Optional]Specifies the last row number in the ordered result set to include in the response. Use this parameter together with **meta_starting_after_row** to define a range of rows for efficient data retrieval. | | meta_starting_after_row | integer | Row Number for selecting activity range after. Could be used for breaking down retrieval into multiple calls (pagination, for example) | [Optional] Indicates the starting row number in the ordered result set, after which rows will be included in the response. Use this parameter together with **meta_ending_at_row** to define a range of rows for efficient data retrieval. | | meta_updated_after | string | Datetime in ISO-8601 format, using UTC time zone | [Optional]Find activities which was updated after given time stamp. Example: If a project has activities that are updated every day in April, and the call is made with **meta_updated_after** = "2022-04-14T14:00:00.001Z. All activities which were modified after that time will be selected. | | meta_updated_prior | string | Datetime in ISO-8601 format, using UTC time zone | [Optional]Find activities which was updated prior given time stamp. | | meta_mapuserfieldtolabel | bool | Define what the attribute for the user fields should contain. | [Optional] The default value is false. Typically the JSON result host uf_textX, uf_dateX, uf_decX, uf_numX, uf_flagX, uf_durX, uf_refX, uf_outX. When set to true, these are replaced with the label as per defined in the database on table userfield_config.label | - When id or item_guid is used, the following will be ignored - meta_ending_at - meta_starting_after - meta_ending_at_row - meta_starting_after_row - meta_updated_after - meta_updated_prior - The following will only be considered when network_id is used: - meta_ending_at - meta_starting_after - meta_ending_at_row - meta_starting_after_row - meta_updated_after - meta_updated_prior - Combining meta_ending_at and meta_starting_after with meta_ending_at_row and meta_starting_after_row is unsupported. - Items marked in grey are only listed for historical reasons and are not implemented. - When specifying subnetwork_id, the network_id must also be specified. - Most of the [Response Fields](/docs/safran-project-integration-api-activities#activities-response-fields) can be used as part of the [Request Fields](/docs/safran-project-integration-api-activities#activities-request-fields). The list of fields below, but not limited too, cannot be used. - duration_units - duration_format - uf_outX - Retrieves activities filtered by Outline Code X. - The uf_outX parameter accepts multiple values separated by the § character, where: - The last value represents the target structure - Any preceding values represent its parent hierarchy - Example: - uf_out2=C2.1§C2.2 - C2.2 is the target structure - C2.1 is its parent - Result - Returns all activities linked to: - Structure C2.2 - Within the hierarchy defined by its parent C2.1 - Notes - Use § as a separator to define hierarchical - Meta_field_exclude, most of the fields listed in the [Response Fields](/docs/safran-project-integration-api-activities#activities-response-fields) can be excluded, except for: - id - network_id - Meta_field_include, most of the fields listed in the [Response Fields](/docs/safran-project-integration-api-activities#activities-response-fields) can be included and excluding all others, except for the following which will always be included: - id - network_id - In the case both "Meta_field_exclude" and "Meta_field_select" is specified the "Meta_field_exclude" takes priority. - meta_mapuserfieldtolabel - When meta_mapuserfieldtolabel is set to true, user field attribute names in the JSON response are replaced with their configured labels. - If the API response contains a user field such as uf_ref1, and the label for Reference Field 1 is defined as “Construction”, the response will return the field using the label name instead of the technical field name. In other words: - uf_ref1 → Construction - uf_ref2 →