cs-selling-experience-api-services icon

cs-selling-experience-api-services

(0 reviews)
This API facilitates secure access to Policy Issuance and Payment Services, designed to support the automation of policy generation, payment processing, and PDF handling

home

๐Ÿ  Home - ๐Ÿ›๏ธ experience-selling-api

Welcome to the documentation for experience-selling-api.
This API handles services related to policy issuance, payments, PDF document generation, and transaction confirmations through channels like PayU.


๐ŸŒ Base Information


๐Ÿš€ Getting Started

  1. Authentication:You must include the client_id and an OAuth 2.0 Bearer token to access secured endpoints.

  2. Required Headers:

    -H "client_id: YOUR_CLIENT_ID"
    -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
  3. Content-Type for POST/PUT:

    -H "Content-Type: application/json"

๐Ÿ“ Available Endpoints

๐Ÿ“„ /PolicyIssuance/v1

MethodEndpointDescriptionLink
POST/PolicyIssuance/v1/generatePolicyGenerates a new policy based on the provided information.View details

๐Ÿ’ณ /Services/v1/Payu

MethodEndpointDescriptionLink
POST/Services/v1/Payu/paymentPayUInitiates a payment with PayU.View details
POST/Services/v1/Payu/paymentConfirmationPayUConfirms the status of a PayU transaction.View details

๐Ÿงพ /Services/v1/ServicePolicyPdf

MethodEndpointDescriptionLink
POST/Services/v1/ServicePolicyPdfRequests the generation of a policy PDF.View details

๐Ÿ’ธ /Services/v1/CorePayment

MethodEndpointDescriptionLink
POST/Services/v1/CorePaymentExecutes the centralized payment flow.View details

๐Ÿ“„ /Services/v1/CorePolicyIssuance

MethodEndpointDescriptionLink
POST/Services/v1/CorePolicyIssuancePerforms the core policy issuance process.View details

๐Ÿ“ค Example Request (POST)

curl -X POST "https://experience-selling-api-qa-v1.us-e1.cloudhub.io/api/PolicyIssuance/v1/generatePolicy" \
-H "Content-Type: application/json" \
-H "client_id: YOUR_CLIENT_ID" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-d '{
  "policyType": "life",
  "customerId": "1234567890",
  "productCode": "PROD001",
  "startDate": "2025-04-01"
}'

โš ๏ธ Error Handling

Standard HTTP status codes are used:

  • 200 OK โ€“ Request was successful
  • 400 Bad Request โ€“ Invalid or missing parameters
  • 401 Unauthorized โ€“ Authentication failed
  • 404 Not Found โ€“ Endpoint or resource not found
  • 500 Internal Server Error โ€“ Unexpected server error

๐Ÿ“ž Support

For any technical issues, please contact:

Integration Services and Applications Coordination
๐Ÿ“ง epalma@fgs.co


๐Ÿ—“๏ธ Notes


Reviews