Resolve API
API that is consumed by the Broker CRM to send a Resolve request containing the borrowers' application details. The Broker CRM receives a response payload of the decision details, as well as an email of the indicative offer sent to the broker.
home
API Type
- External API
Supported Protocols
- HTTPS
Accepts
- application/xml
Responds With
- application/xml
Authentication
- Client Credentials - via MuleSoft API Manager - pass Basic authentication credentials as Authorization header in the request
Endpoint Quick Reference
/v1/resolve/au
- POST - Endpoint for sending request to the Decision Engine and process a resolve application.
Status Response Codes
- 200: OK Success.
- 201: Created (for POST and PATCH method).
- 400: Bad Request - Check if your request body or request headers match the specification, or if mandatory fields and correct data types are provided.
- 401: Unauthorized - Check if your credentials are correct.
- 404: Resource Not Found - Check if you have the correct resource URI.
- 405: Method Not Allowed - Check if you have valid methods for the resource.
- 408: Request Timeout - The API could be still processing your request, try to adjust connection timeout.
- 500: Unexpected Server Error - If this issue persists, contact support for troubleshooting.
- 503: Service Unavailable - Server is handling too many request at this moment. Try again later or reach out to support if issue persists.
- 504: Gateway Timeout - There might be a problem with the load-balancer, reach out to support if issue persists.
Contact
- Pavithra Sugumar - psugumar@pepper.com.au
- Ralph Palomar - rpalomar@pepper.com.au
- Jamie Ng - jng@pepper.com.au
- Peter Ng - png@pepper.com.au