Payment Request Details API
Payment APIs
Payment Request Details API
Retrieve a single payment request (vendor advance) by its identifier
Payment Request Details API
Authentication
All requests require an API key in the request headers. Headers:Request
Path Parameters
Only payment requests of type
VENDOR_ADVANCE are supported today. Requesting any other payment request type returns a 400 VALIDATION_ERROR — see Error Responses.Code Examples
Success Response
HTTP Status:200 OK
Response Fields:
Tags Object
tags is keyed by tag/field slug. Predefined organization tags (cost centre, department, location, expense head) carry the selected value’s id alongside its value; custom fields carry only a value.
Response Example
Error Responses
Validation Errors
HTTP Status:400 Bad Request
Returned when paymentRequestId fails schema validation (empty, or longer than 100 characters).
Unsupported Payment Request Type
HTTP Status:400 Bad Request
The identifier resolves to a payment request that isn’t a vendor advance (e.g. a direct payment, reimbursement group, or bulk payout).
Payment Request Not Found
HTTP Status:404 Not Found
Access Denied
HTTP Status:403 Forbidden
The API key’s user is not an admin or bookkeeper:
Authentication Errors
HTTP Status:401 Unauthorized
Permission Errors
HTTP Status:403 Forbidden
Best Practices
- Use
tax.subTotal(notamount) when you need the pre-tax value the advance was raised for —amountis the net payable after GST, TDS and round-off - Treat
purchaseOrderLinkandpayeras optional; both arenullfor advances raised without a PO link or before a payer is resolved - Poll
state,approvalStateandpaymentStatetogether to track a request end-to-end:statecovers approval,paymentStatecovers settlement - Store the
paymentRequestIdreturned by Vendor Advance Creation at create time rather than looking the request up by sequence number later