cs-webhook-xapi
This API is designed to receive automatic submissions from applications, ensuring seamless integration and real-time data processing
home
🏠 Home - 📡cs-webhook-xapi
This API enables the reception of automatic submission events from applications. It functions as a webhook primarily designed to receive confirmations from external services such as PayU.
The main endpoint available allows integration with the PayU Web Checkout confirmation flow.
🌐 Base Information
- API Title: cs-webhook-xapi
- Version: 1.0.0
- Base URL:
https://cs-webhook-xapi-{env}v1.us-e1.cloudhub.io/
- Environments:
dev
,qa
,prod
- Protocols Supported: HTTPS
- Exchange Link: cs-webhook-xapi on Exchange
🚀 Getting Started
- Environment Selection: Replace
{env}
in the base URL with one of the available environments (dev
,qa
,prod
). - Authentication: This API is public-facing and does not require authentication (webhook style).
- Headers: All requests should include:
Content-Type: application/json
📍 Available Endpoints
📌 Endpoints Overview
Method | Endpoint | Description | Exchange Link |
---|---|---|---|
POST | /payu/web-checkout/confirmation | Receives payment confirmation data from PayU after checkout. | View details |
📤 Example Request
curl -X POST "https://cs-webhook-xapi-devv1.us-e1.cloudhub.io/payu/web-checkout/confirmation" \
-H "Content-Type: application/json" \
-d '{
"transactionId": "123456789",
"status": "APPROVED",
"paymentMethod": "VISA",
"amount": 150000
}'
📚 Modules & Libraries Used
commons
:fragment-library-commons.raml
lib-types
:types/library-types.raml
⚠️ Error Handling
Standard HTTP status codes are used for error handling:
200 OK
– Request was successful400 Bad Request
– Missing or invalid parameters401 Unauthorized
– Authentication failed404 Not Found
– Endpoint or resource not found500 Internal Server Error
– Unexpected error on the server
📞 Support
For any issues, please contact the API support team:
Integration Services and Applications Coordination
📧 epalma@fgs.co
📅 Notes
- Documentation last updated: April 2025
- For further updates, refer to the API Exchange Portal