post

/v1/policies

Create policy.

When developing in our Partner Development Environment, the approval_status of a policy will always match the approval_status of the primary driver on the policy. So to force a policy to be a certain status, you should force a driver to that status first, and then create a policy with that driver as the primary driver.

The API can be used to make some modifications to a policy. Any of the following transactions can be made up to 48 hours after the currently scheduled end date and time of the policy; any attempts to make a change after that time will result in an error. Note that any changes made to a policy may change the price of the policy.

Authorization

bearer

Request Body

2 Examples
Schema
object
$schema: http://json-schema.org/draft-04/schema#
policy
object
1 validation + required

Responses

OK

Schema
object
$schema: http://json-schema.org/draft-04/schema#
id
integer

Unique id assigned by DigiSURE.

4 validations
partner_transaction_id
string

Your tracking id. Typically a reservation or trip id, but available for use at your discretion.

1 validation
quote_id
integer

id of quote that originated this policy.

4 validations + required
bind_time
string

Depracated

2 validations
custom_fields
object
status
string

Policy status describes the status of coverage.

‘bound’-coverage is in place.

‘unbound’-coverage is not in place

‘cancelled’- Policy no longer exists and cannot be bound.

1 validation
approval_status
string

Describes the current status in the approval process. In the development environment, the Value of approval_status in Policy object is always identical to the value in the primary Driver object for the same quote id.

1 validation

Send a Test Request

Send requests directly from the browser (CORS must be enabled)
$$.env
1 variable not set
bearer_token