Skip to main content

Payin - Recon File

Endpoint: POST /api/v1/payin/reconFile

Headers:

  • token: <string> (API token)
  • Content-Type: application/json

Request body:

{
  "date": "2026-03-04"
}

Example curl:

curl --location '{ROOT_URL}/api/v1/payin/reconFile' \
  --header 'token: 0a1225c5-0930-4c55-b318-f530eb3333b9' \
  --header 'Content-Type: application/json' \
  --data '{"date": "2026-03-04"}'

Example response (job queued):

{
  "logId": "2wasdMZttp0UM00NAps0",
  "status": true,
  "message": "Export job queued",
  "data": {
    "jobId": "6527b5959ee883846f7c",
    "note": "Request accepted; re-submit same request to check status; will return download URL when ready"
  }
}

Example response (export ready):

{
  "logId": "20ExtHQSUb4qT3CheVLD",
  "status": true,
  "message": "Export ready",
  "data": {
    "jobId": "6527b5959ee883846f7c",
    "download": "https://.../recon_2026-03-04_6527b5959ee883846f7c.csv?X-Amz-..."
  }
}

Explanation:

  • date: recon date to export (format YYYY-MM-DD).
  • On the first request, the API queues an export job and returns a jobId.
  • If the job is not finished yet, send the same request again to check its status.
  • Once completed, the response includes download, a temporary URL to download the recon CSV.

Main response fields:

  • logId: request log ID.
  • status: boolean, true when successful.
  • message: short status message.
  • data.jobId: export job ID.
  • data.download: (when ready) presigned URL to download the CSV file.

Security notes:

  • Download URLs are usually temporary (presigned) and have an expiration time.
  • Keep your API token secure and never commit it to the repository.