Tenant tag
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/
Bodyapplication/json
Full request structure per product can be taken from json scheme Product json scheme. with type: policy and name: {name of the insurance product}.
any
- Mock server
https://ledger.docs.insly.com/_mock/apis/ledger/bundled/api/v1/ledger/sales/policies/{policyId}/bind
- Beta
https://ledger.app.beta.insly.training/api/v1/ledger/sales/policies/{policyId}/bind
- Demo
https://ledger.app.demo.insly.com/api/v1/ledger/sales/policies/{policyId}/bind
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://ledger.docs.insly.com/_mock/apis/ledger/bundled/api/v1/ledger/sales/policies/{policyId}/bind' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-TENANT-ID: {$inputs.tenant}' \
-d '{}'