Account jobs, job groups, and policies

You can view the list of jobs, job groups, and policies associated with an account. You can also move policies and unbound submissions from one account to another.

For information about moving unbound submissions from one account to another, see Moving submissions between accounts.

Querying for job information

To retrieve a list of jobs for a given account, use the following endpoints:

  • GET /account/v1/accounts/{accountId}/jobs

By default, only open jobs are returned. To see all jobs, add a filter query parameter such as this:

GET /accounts/{AccountId}/jobs?filter=*none

See Endpoints with default filters for more information on default filters.

Note that there could also be authorization filters based on the account holder. See Cloud API Developer Guide for more information.

Querying for job group information

To retrieve job groups for a given account, use the following endpoints:
  • GET /account/v1/accounts/{accountId}/job-groups
  • GET /account/v1/accounts/{accountId}/job-groups/{jobGroupsId}

For more information about job groups, see

Querying for policy information

To retrieve a list of policies for a given account, use the following endpoint:
  • GET /account/v1/accounts/{accountId}/policies

Moving policies

In some situations, you may want to move a policy from a source account to a target account. For example, this could be necessary if the policy was erroneously associated with the wrong account.

To move a policy to a given target account, use the following endpoint:

  • POST /account/v1/accounts/{accountId}/move-policies

The POST is executed from the target account (the account that will own the policy moving forward). The request object requires a request payload that specifies the IDs of the policies to move to the target account. These IDs are specified in a policies array.

For example, the following call moves the policies with IDs pc:1021 and pc:1099 to account pc:477.

POST /account/v1/accounts/pc:477/move-policies

{
  "data": {
    "attributes": {
      "policies": [
        {
          "id": "pc:1021"
        },
        {
          "id": "pc:1099"
        }
      ]
    }
  }
}

The "move policies" functionality has the following limitations:

  • You cannot move an archived policy.
  • You cannot move multiple policies at one time from different source accounts. Every group of moved policies must be from the same source account going to the same target account.
  • You cannot move a policy to an account that could not normally own that type of policy. (For example, you cannot move a Personal Auto policy to an account that is a company.)
  • All InsuranceSuite applications have a Messaging infrastructure used to send messages asynchronously to third-party applications. You cannot move a policy if it has any pending messages associated with it.

For information about moving unbound submissions from one account to another, see Moving submissions between accounts.