Procore.Api.ProjectManagementMeetingsMeetingTopics (procore_sdk v0.3.0)

API calls for all endpoints tagged ProjectManagementMeetingsMeetingTopics.

Summary

Functions

rest_v10_meeting_topics_id_patch(connection, procore_company_id, id, body67, opts \\ [])

Update meeting topic Update an existing Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

rest_v10_meeting_topics_parent_minutes_get(connection, procore_company_id, meeting_id, meeting_topic_id, opts \\ [])

Get the minutes and date created for all parent topics Returns an array of objects of minutes and created_on values for all parent meeting topics

rest_v10_meeting_topics_post(connection, procore_company_id, body67, opts \\ [])

Create meeting topic Creates Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

rest_v11_projects_project_id_meeting_topics_id_patch(connection, procore_company_id, project_id, id, body66, opts \\ [])

Update meeting topic Update an existing Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

rest_v11_projects_project_id_meeting_topics_meeting_topic_id_parent_minutes_get(connection, procore_company_id, project_id, meeting_id, meeting_topic_id, opts \\ [])

Get the minutes and date created for all parent topics Returns an array of objects of minutes and created_on values for all parent meeting topics

rest_v11_projects_project_id_meeting_topics_post(connection, procore_company_id, project_id, body66, opts \\ [])

Create meeting topic Creates Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

Functions

Link to this function

rest_v10_meeting_topics_id_patch(connection, procore_company_id, id, body67, opts \\ [])

@spec rest_v10_meeting_topics_id_patch(
  Tesla.Env.client(),
  integer(),
  integer(),
  Procore.Model.Body67.t(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     Procore.Model.RestV10MeetingsPost201ResponseMeetingCategoriesInnerMeetingTopicInner.t()}
  | {:error, Tesla.Env.t()}

Update meeting topic Update an existing Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • id (integer()): ID of the meeting topic
  • body67 (Body67):
  • opts (keyword): Optional parameters

Returns

  • {:ok, Procore.Model.RestV10MeetingsPost201ResponseMeetingCategoriesInnerMeetingTopicInner.t} on success
  • {:error, Tesla.Env.t} on failure
Link to this function

rest_v10_meeting_topics_parent_minutes_get(connection, procore_company_id, meeting_id, meeting_topic_id, opts \\ [])

@spec rest_v10_meeting_topics_parent_minutes_get(
  Tesla.Env.client(),
  integer(),
  integer(),
  integer(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     [Procore.Model.RestV10MeetingTopicsParentMinutesGet200ResponseInner.t()]}
  | {:error, Tesla.Env.t()}

Get the minutes and date created for all parent topics Returns an array of objects of minutes and created_on values for all parent meeting topics

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • meeting_id (integer()): ID of the meeting
  • meeting_topic_id (integer()): ID of the meeting topic
  • opts (keyword): Optional parameters

Returns

  • {:ok, [%RestV10MeetingTopicsParentMinutesGet200ResponseInner{}, ...]} on success
  • {:error, Tesla.Env.t} on failure
Link to this function

rest_v10_meeting_topics_post(connection, procore_company_id, body67, opts \\ [])

@spec rest_v10_meeting_topics_post(
  Tesla.Env.client(),
  integer(),
  Procore.Model.Body67.t(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     Procore.Model.RestV10MeetingsPost201ResponseMeetingCategoriesInnerMeetingTopicInner.t()}
  | {:error, Tesla.Env.t()}

Create meeting topic Creates Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • body67 (Body67):
  • opts (keyword): Optional parameters

Returns

  • {:ok, Procore.Model.RestV10MeetingsPost201ResponseMeetingCategoriesInnerMeetingTopicInner.t} on success
  • {:error, Tesla.Env.t} on failure
Link to this function

rest_v11_projects_project_id_meeting_topics_id_patch(connection, procore_company_id, project_id, id, body66, opts \\ [])

@spec rest_v11_projects_project_id_meeting_topics_id_patch(
  Tesla.Env.client(),
  integer(),
  integer(),
  integer(),
  Procore.Model.Body66.t(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     Procore.Model.RestV11ProjectsProjectIdMeetingTopicsPost201Response.t()}
  | {:error, Tesla.Env.t()}

Update meeting topic Update an existing Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • project_id (integer()): Unique identifier for the project.
  • id (integer()): ID of the Meeting Topic
  • body66 (Body66):
  • opts (keyword): Optional parameters

Returns

  • {:ok, Procore.Model.RestV11ProjectsProjectIdMeetingTopicsPost201Response.t} on success
  • {:error, Tesla.Env.t} on failure
Link to this function

rest_v11_projects_project_id_meeting_topics_meeting_topic_id_parent_minutes_get(connection, procore_company_id, project_id, meeting_id, meeting_topic_id, opts \\ [])

@spec rest_v11_projects_project_id_meeting_topics_meeting_topic_id_parent_minutes_get(
  Tesla.Env.client(),
  integer(),
  integer(),
  integer(),
  integer(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     [
       Procore.Model.RestV11ProjectsProjectIdMeetingTopicsMeetingTopicIdParentMinutesGet200ResponseInner.t()
     ]}
  | {:error, Tesla.Env.t()}

Get the minutes and date created for all parent topics Returns an array of objects of minutes and created_on values for all parent meeting topics

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • project_id (integer()): Unique identifier for the project.
  • meeting_id (integer()): ID of the meeting
  • meeting_topic_id (integer()): ID of the meeting topic
  • opts (keyword): Optional parameters

Returns

  • {:ok, [%RestV11ProjectsProjectIdMeetingTopicsMeetingTopicIdParentMinutesGet200ResponseInner{}, ...]} on success
  • {:error, Tesla.Env.t} on failure
Link to this function

rest_v11_projects_project_id_meeting_topics_post(connection, procore_company_id, project_id, body66, opts \\ [])

@spec rest_v11_projects_project_id_meeting_topics_post(
  Tesla.Env.client(),
  integer(),
  integer(),
  Procore.Model.Body66.t(),
  keyword()
) ::
  {:ok,
   Procore.Model.RestV10CompaniesCompanyIdWorkflowPermanentLogsGet401Response.t()}
  | {:ok,
     Procore.Model.RestV11ProjectsProjectIdMeetingTopicsPost201Response.t()}
  | {:error, Tesla.Env.t()}

Create meeting topic Creates Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files.

Parameters

  • connection (Procore.Connection): Connection to server
  • procore_company_id (integer()): Unique company identifier associated with the Procore User Account.
  • project_id (integer()): Unique identifier for the project.
  • body66 (Body66):
  • opts (keyword): Optional parameters

Returns

  • {:ok, Procore.Model.RestV11ProjectsProjectIdMeetingTopicsPost201Response.t} on success
  • {:error, Tesla.Env.t} on failure