TRANXACT.AI Help

India statutory · Records

Upi settlement lines

Read and maintain upi settlement lines records (india.upi_settlement_detail).

Type REST6 operationsBase path /api/india/upi-settlement-linesPublished as /api/v1/upi-settlement-lines

Download specification (OpenAPI 3.1)

Overview

PackageIndia statutory
AuthenticationBearer token: a service account's token (POST /api/auth/service-token) or, for the published path, an API key
AuthorizationThe caller's roles must hold India statutory › Upi settlement lines on the Roles screen: display for GET, add for POST, change for PUT, delete for DELETE; an action needs the grant of the button that runs it on the screen.
Tableindia.upi_settlement_detail · kept per company (and organisational unit where it has one)
RecordRead only; key id
RulesThe same as the screen: validation, numbering, approvals, posting, the company the caller belongs to, and the audit trail.

API reference

6 operations. Open one for its parameters, bodies, responses and a sample request.

GET/api/india/upi-settlement-linesList upi settlement lines

Query parameters

NameDescriptionExample
limitRows per page (50 by default, at most 200)limit=100
offsetRows to skipoffset=200
qFree-text search over the search columnsq=acme
sortcolumn:asc or column:desc, several separated by commassort=created_at:desc
filterA JSON condition or group (see the filter language), URL-encoded; any field below can be filtered and sortedfilter={"col":"status","op":"eq","value":"open"}
<field>=<value>Shorthand for "field is value" 

Response 200

{
  "rows": [
    {
      "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
      "settlement_no": "SET-000001",
      "settlement_date": "2026-10-30",
      "line_no": 10,
      "rrn": "text",
      "transaction_ref": "text",
      "amount": "1250.00",
      "value_date": "2026-10-30",
      "utr": "text",
      "matched_by": "text",
      "outcome": "text",
      "note": "text",
      "txn_no": "TXN-000001",
      "source_no": "SOU-000001"
    }
  ],
  "count": 1
}

Sample request

curl "https://demo.tranxact.ai/api/india/upi-settlement-lines?limit=20" \
  -H "Authorization: Bearer $TOKEN"
GET/api/india/upi-settlement-lines/{id}Read one upi settlement lines

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Response 200

{
  "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "settlement_no": "SET-000001",
  "settlement_date": "2026-10-30",
  "line_no": 10,
  "rrn": "text",
  "transaction_ref": "text",
  "amount": "1250.00",
  "value_date": "2026-10-30",
  "utr": "text",
  "matched_by": "text",
  "outcome": "text",
  "note": "text",
  "txn_no": "TXN-000001",
  "source_no": "SOU-000001"
}

404 when no record with that id is visible to the caller.

Sample request

curl "https://demo.tranxact.ai/api/india/upi-settlement-lines/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN"
POST/api/india/upi-settlement-linesPost upi settlement lines

No body is required.

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X POST "https://demo.tranxact.ai/api/india/upi-settlement-lines" \
  -H "Authorization: Bearer $TOKEN"
POST/api/india/upi-settlement-lines/{id}/copyCopy

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Request body

The keys this action reads (* = required; "one of" lists the only values):

overrides, preview, withLines

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X POST "https://demo.tranxact.ai/api/india/upi-settlement-lines/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73/copy" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"overrides":"value","preview":"value","withLines":"value"}'
PUT/api/india/upi-settlement-lines/{id}Put upi settlement lines

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

No body is required.

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X PUT "https://demo.tranxact.ai/api/india/upi-settlement-lines/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN"
DELETE/api/india/upi-settlement-lines/{id}Delete upi settlement lines

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

No body is required.

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X DELETE "https://demo.tranxact.ai/api/india/upi-settlement-lines/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN"

Data model

Every field of a upi settlement lines, as the API returns it. Field names are the JSON keys; any of them can be filtered and sorted on a list.

FieldTypeAccessDescription
iduuidread onlyId
org_iduuidread onlyOrg id
settlement_notextread onlySettlement no
settlement_datedateread onlySettlement date
line_nointegerread onlyLine no
rrntextread onlyRrn
transaction_reftextread onlyTransaction ref
amountnumericread onlyAmount
value_datedateread onlyValue date
utrtextread onlyUtr
matched_bytextread onlyMatched by
outcometextread onlyOutcome
notetextread onlyNote
txn_notextread onlyTxn no
source_notextread onlySource no
expected_amountnumericread onlyExpected amount
payment_statustextread onlyPayment status
settlement_iduuidread onlySettlement id
transaction_iduuidread onlyTransaction id

Errors

StatusMeaning
400The request could not be read: a filter that is not JSON, a bad parameter
401No credential, or it is wrong, revoked or expired
403The caller's roles do not hold India statutory › Upi settlement lines for this verb, or the address or origin is not allowed
404No record with that id is visible to the caller
409A conflict: a duplicate number, a document in a state that does not allow it, or a record changed or locked by someone else
422Refused by the same validation as the screen; the error names the field and why

Every error is JSON: {"error": "a sentence saying what was wrong"}, with field where it applies.