cs-selling-experience-api-services icon

cs-selling-experience-api-services

2.1.x
(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 - Experience Selling API

Welcome to the Experience Selling API documentation. This API facilitates secure access to Policy Issuance and Payment Services, designed to support the automation of policy generation, payment processing, and PDF handling.

🌐 Base Information

  • API Title: Experience Selling API
  • Version: 1.0.0
  • Base URL:
    https://<your-domain>/v1/
  • Authentication URL:
    https://authentication-services-colmena-{{env}}.us-e1.cloudhub.io/token

🚀 Getting Started

  1. Authentication: Ensure you have the required client_id and OAuth 2.0 Bearer token for secure access.
  2. Base URL: Use the provided Base URL as the prefix for all API endpoints.
  3. Headers: Add the following headers in your API requests:
    -H "client_id: YOUR_CLIENT_ID" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"

📍 Endpoints

1️⃣ POST /PolicyIssuance/v1/generatePolicy

  • Description: Generate new insurance policies.
  • Request Body: JSON with policy details.
Example Request:
curl -X POST "https://<your-domain>/v1/PolicyIssuance/generatePolicy" \
  -H "Content-Type: application/json" \
  -H "client_id: YOUR_CLIENT_ID" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d @GeneratePolicyRequestExample.json

2️⃣ POST /Services/v1/Payu/paymentPayU

  • Description: Process payments using PayU.
  • Request Body: JSON with payment details.
Example Request:
curl -X POST "https://<your-domain>/v1/Services/Payu/paymentPayU" \
  -H "Content-Type: application/json" \
  -H "client_id: YOUR_CLIENT_ID" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d @PagoPayURequestExample.json

3️⃣ POST /Services/v1/Payu/paymentConfirmationPayU

  • Description: Confirm PayU payment transactions.
  • Request Body: JSON with confirmation details.
Example Request:
curl -X POST "https://<your-domain>/v1/Services/Payu/paymentConfirmationPayU" \
  -H "Content-Type: application/json" \
  -H "client_id: YOUR_CLIENT_ID" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d @PaymentConfirmationRequestExample.json

4️⃣ POST /Services/v1/ServicePolicyPdf

  • Description: Generate or process PDF versions of insurance policies.
  • Request Body: JSON with policy information for PDF generation.
Example Request:
curl -X POST "https://<your-domain>/v1/Services/ServicePolicyPdf" \
  -H "Content-Type: application/json" \
  -d @PolicyPdfRequestExample.json

5️⃣ POST /Services/v1/CorePayment

  • Description: Handle core payment transactions.
  • Request Body: JSON with payment data.
Example Request:
curl -X POST "https://<your-domain>/v1/Services/CorePayment" \
  -H "Content-Type: application/json" \
  -H "client_id: YOUR_CLIENT_ID" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d @CorePaymentRequestExample.json

6️⃣ POST /Services/v1/CorePolicyIssuance

  • Description: Issue insurance policies through core services.
  • Request Body: JSON with policy issuance data.
Example Request:
curl -X POST "https://<your-domain>/v1/Services/CorePolicyIssuance" \
  -H "Content-Type: application/json" \
  -H "client_id: YOUR_CLIENT_ID" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d @PolicyIssuanceCoreRequestExample.json

⚠️ Error Handling

Standard HTTP status codes are used for error handling:
- 200 OK - Request successful.
- 400 Bad Request - Missing/invalid parameters.
- 401 Unauthorized - Authentication failure.
- 404 Not Found - Resource not found.
- 500 Internal Server Error - Server error.

📞 Support

For any questions or issues, please contact the API support team at INTEGRATION SERVICES AND APPLICATIONS COORDINATION.

Notes

  • Documentation updated in February 2025.
  • For additional information, contact: epalma@fgs.co

Reviews