Issuing a previously bound policy

Issuance refers to the action of issuing a policy that was previously bound but unissued. From a technical standpoint, issuance is a policy transaction.

  • Issuance does not involve the original submission job. That job is considered to be concluded when the policy was bound.
  • Similar to policy change and renewal:
    • Issuance jobs are created from the policy.
    • Issuance jobs can modify the policy contents.
    • Issuance jobs must be quoted and completed.

To issue a previously bound policy, you must:

  1. Initiate the issuance job from the policy.
  2. Modify the job as needed. This could involve specifying information that was not available when the policy was bound.
  3. Quote the issuance job.
  4. Complete the issuance job.

Initiate the issuance job

Use the following endpoint to issue a previously bound but unissued policy. Note that this endpoint is in the Policy API and is executed from the policy:

  • POST /policy/v1/policies/{policyId}/issue

The request object requires an empty request body.

For example, the following creates an issuance job for policy pc:919.

POST /job/v1/jobs/pc:919/issue

{
  "data": {
    "attributes": {
    }
  }
}

This creates a new job instance whose job type is "Issuance" and whose status is "Draft". For the purposes of the following examples, assume that the ID of this job is pc:8808.

Modify the issuance job as needed

To modify the job, use the Job API endpoints to specify information as if it were part of the original submission.

Quote the issuance job

To quote the issuance job, use the following endpoint:

  • POST /job/v1/jobs/{jobId}/quote

The request object does not require a body.

For example, the following request quotes job pc:8808:

POST /job/v1/jobs/pc:8808/quote

<no request body>

If the quote at issuance is different than the quote when bound, this typically triggers an additional billing request to either charge for or credit the difference.

Complete the issuance job

There is no /issue-only endpoint. To successfully complete an issuance job, you must use the /bind-and-issue endpoint.

For example, the following request binds and issues issuance job pc:8808.

POST /job/v1/jobs/pc:8808/bind-and-issue

<no request body>

You can also withdraw the issuance job. For example, this might be appropriate if the issuance included significantly erroneous information. To withdraw an issuance job, use the following endpoint:

  • POST /job/v1/jobs/{jobId}/withdraw

The request object does not require a body.

For example, the following request withdraws job pc:4040.

POST /job/v1/jobs/pc:8808/withdraw

<no request body>