Skip to content

Ledger/Sales service (1.0)

Using Swagger documentation in Postman


You can find instructions on how to convert swagger documentation to Postman collection here.
There is a known problem in Postman with env variables being imported as parameters (:schemaName instead of {{schemaName}}. More info on the issue can be found here.
Possible workaround is to find and replace all parameters with env variables inside Postman. For example search for :schemaName and replace with {{schemaName}}. Instructions how to do it in Postman are here.

Authorization

To obtain a token, start by visiting the identifier service documentation and make a request with your username and password.
Once you receive the response, copy the access_token and use it for making requests to ledger services.
Download OpenAPI description
Languages
Servers
Mock server

https://ledger.docs.insly.com/_mock/apis/ledger/bundled/

Beta

https://ledger.app.beta.insly.training/

Demo

https://ledger.app.demo.insly.com/

Operations
Operations
Operations
Operations
Operations
Operations

Request

It's async request, UI sends "actions" endpoint and waits until lock is released

Security
bearerAuth
Path
policyIdstringrequired
Headers
X-TENANT-IDstringrequired

Tenant tag

Example: {$inputs.tenant}
Bodyapplication/jsonrequired

Send quote to referral comment

commentstring
Example: "Reason of sending quote to referral"
curl -i -X POST \
  'https://ledger.docs.insly.com/_mock/apis/ledger/bundled/api/v1/ledger/sales/policies/{policyId}/referrals' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'X-TENANT-ID: {$inputs.tenant}' \
  -d '{
    "comment": "Reason of sending quote to referral"
  }'

Responses

Quote has been sent to referral

Bodyapplication/json
Response
application/json

No content

Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations