Creating activities

Use the following endpoints to create activities:

ClaimCenter:
- POST claim/v1/claims/{claimId}/activities: The activity must be created from an existing claim.
PolicyCenter:
- POST account/v1/accounts/{accountId}/activities: The activity must be created from an existing account.
- POST job/v1/jobs/{jobId}/activities: The activity must be created from an existing job.
- POST policy/v1/policies/{policyId}/activities: The activity must be created from an existing policy.
BillingCenter:
- POST /common/v1/activities: Create either a shared activity (SharedActivity subtype) or an assigned activity (Activity subtype).

There are some different requirements when creating activities in BillingCenter than in ClaimCenter or PolicyCenter. See

Creating activities from activity patterns

Activities can be created from activity patterns. An activity pattern is a set of default values for fields in the activity (such as description, subject, and priority). Every activity pattern has a code, such as contact_insured or legal_review.

When creating a PolicyCenter or ClaimCenter activity through Cloud API, the only required field is activityPattern, which must specify the activity pattern's code. Because the activity pattern typically contains all the necessary default values, the activity pattern is often the only field the caller application needs to specify.

You can retrieve a list of activity patterns using the following endpoints for your respective InsuranceSuite application:

ClaimCenter:
- GET /claim/v1/claims/{claimId}/activity-patterns
PolicyCenter:
- GET /account/v1/accounts/{accountId}/activity-patterns
- GET /job/v1/jobs/{jobId}/activity-patterns
- GET /policy/v1/policies/{policyId}/activity-patterns
BillingCenter:
- There is currently no endpoint for retrieving activity patterns in BillingCenter.

You can optionally specify values for the following fields, each of which overrides the value coming from the activity pattern:


Field	Datatype	Description	Default
`description`	string	The activity's description	Typically comes from the activity pattern
`dueDate`	datetime	The date by which the activity is expected to be completed	Typically calculated based on values in the activity pattern
`escalationDate`	datetime	The date on which the activity will be escalated if it has not yet been completed	Typically calculated based on values in the activity pattern
`externallyOwned`	Boolean	Whether the activity is to be assigned to an external group or external user	Typically comes from the activity pattern
`importance`	Typekey (a value from the `ImportanceLevel` typelist)	The activity's importance, as reflected on the user's calendar	Typically comes from the activity pattern
`mandatory`	Boolean	Whether the activity must be completed (true) or can be skipped (false)	Typically comes from the activity pattern
`priority`	Typekey (a value from the `Priority` typelist)	The activity's priority	Typically comes from the activity pattern
`recurring`	Boolean	Whether the activity repeats. If true, completing the activity creates a new one.	Typically comes from the activity pattern
`subject`	String	The activity's subject	Typically comes from the activity pattern

AutomatedOnly activity patterns

Activity patterns have an AutomatedOnly field. This field designates whether or not a user can create activities through the user interface using that activity pattern.

Note: The AutomatedOnly is only available to users of the ClaimCenter specific Cloud API.

false - users can create activities with this activity pattern through the user interface
true - users cannot create activities with this activity pattern through the user interface

When a caller attempts to create an activity through Cloud API, the default behavior is to prohibit the use of any activity pattern whose AutomatedOnly field is set to true.

There is a system permission named restcreateautomatedactivity that can be used to override this behavior. If a caller has some association with this permission, then that caller can create activities from AutomatedOnly activity patterns. There are two ways this association can exist.

For more information on how to associate this permission with different types of callers, see Cloud API Developer Guide.

Examples of creating activities from activity patterns

The following is an example of creating a contact_insured activity in PolicyCenter for account pc:10. The activity defaults to all values in the contact_insured activity pattern.

Command

POST /account/v1/accounts/pc:10/activities

Request

{
  "data": {
    "attributes": {
      "activityPattern": "contact_insured"
    }
  }
}

The following is an example of creating a legal_review activity in PolicyCenter for account pc:10. In this case, two activity pattern values are overridden: the activity is mandatory (it cannot be skipped) and the priority is urgent.

Command

POST /account/v1/accounts/pc:10/activities

Request

{
  "data": {
    "attributes": {
      "activityPattern": "legal_review",
      "mandatory": true,
      "priority": {
        "code": "urgent"
      }
    }
  }
}

Creating activities in BillingCenter

When creating activities in BillingCenter, you can provide the values for the activity field in one of two ways, but not both:

Activity pattern: Provide an activityPattern code. The API populates the activity's fields from the pattern. You cannot set any of the following fields when using an activity pattern: command, description, documentTemplate, dueDate, emailTemplate, escalationDate, mandatory, priority, recurring, or subject.
Individual fields: Omit activityPattern and provide individual fields directly. In this case, several fields are required, as detailed in the table below.

You must also specify the activity subtype to define how the activity is assigned.

SharedActivity: An activity visible to a group but not assigned to a specific user.
Activity: An assigned activity. The initialAssignment field (specifying a group and optional user) is required for this subtype.

The following fields are available when creating activities in BillingCenter:


Field	Description	Note
`subtype`	The activity subtype: `Activity` or `SharedActivity`.	Required.
`initialAssignment`	The group and optional user to assign the activity to on creation.	Required for the `Activity` subtype. Optional otherwise. If only a group is provided, the activity is assigned to a user in the group based on assignment rules.
`activityPattern`	The code of an activity pattern, as a string. Populates activity fields from the pattern.	Optional. If this field is set, you cannot set the fields below.
`subject`	The activity's subject line.	Required when not using `activityPattern`. Cannot be used with `activityPattern`.
`priority`	The activity's priority (a value from the `Priority` typelist).	Required when not using `activityPattern`. Cannot be used with `activityPattern`.
`command`	A Gosu command to execute for this activity.	Optional. Cannot be used with `activityPattern`.
`description`	The activity's description.	Optional. Cannot be used with `activityPattern`.
`documentTemplate`	A document template associated with this activity.	Optional. Cannot be used with `activityPattern`.
`dueDate`	The date by which the activity is expected to be completed.	Optional. Cannot be used with `activityPattern`.
`emailTemplate`	An email template associated with this activity.	Optional. Cannot be used with `activityPattern`.
`escalationDate`	The date on which the activity escalates if not completed.	Optional. Cannot be used with `activityPattern`.
`mandatory`	Whether the activity must be completed (`true`) or can be skipped (`false`).	Optional. Cannot be used with `activityPattern`.
`recurring`	Whether completing the activity automatically creates a new one.	Optional. Cannot be used with `activityPattern`.

Create a shared activity using an activity pattern

When the activityPattern field is set, the only other required field is subtype.

Request

POST /common/v1/activities

{
  "data": {
    "attributes": {
      "activityPattern": "notification",
      "subtype": {
        "code": "SharedActivity"
      }
    }
  }
}

Create an assigned activity using individual fields

The minimal required fields are initialAssignment, priority, subject, and subtype. The following request also includes a description, a due date, and the user the activity is assigned to.

Request

POST /common/v1/activities

{
  "data": {
    "attributes": {
      "subject": "Review policy renewal",
      "description": "Review the upcoming policy renewal for this account.",
      "dueDate": "2026-05-01",
      "priority": {
        "code": "normal"
      },
      "subtype": {
        "code": "Activity"
      },
      "initialAssignment": {
        "groupId": "bc:group-123",
        "userId": "bc:user-456"
      }
    }
  }
}