Monitoring & History

This endpoint allows you to retrieve the status, risk analysis results, and notification history of your transactions. You can query a specific transaction or fetch a filtered list of historical operations.

URL: https://app.rillis.io/api/v1/verification/get

Method: GET

API Reference: To see the technical details, parameters, and live testing for this process, go to:
GET - List Transactions

Request Parameters (Query Strings)

All parameters below must be appended to the URL as query strings.

1. Mandatory Authentication

Parameter	Type	Required	Description
`client_id`	String	Yes	Your unique client identifier.
`client_secret`	String	Yes	Your secret API key.

2. Search & Filtering

Parameter	Type	Required	Description
`external_transaction_id`	String	No	Filter by your internal transaction ID.
`page`	Number	No	Page number for pagination (Default: `1`).
`limit`	Number	No	Items per page (Default: `10`, Max: `100`).

Example Request (Single Transaction)

GET https://app.rillis.io/api/v1/verification/get?client_id=your_client_id&client_secret=your_client_secret&external_transaction_id=transaction_12345

Example Request (Multiple Transactions)

GET https://app.rillis.io/api/v1/verification/get?client_id=your_client_id&client_secret=your_client_secret&page=1&limit=20

Response

The response returns a paginated object containing an array of items.

Root Properties

Parameter	Type	Description
`items`	Array	List of transaction analysis reports.
`totalItems`	Number	Total count of transactions matching the filters.
`totalPages`	Number	Total pages available.

Item Object Details (The Analysis)

Parameter	Type	Description
`external_transaction_id`	String	The ID provided by you during the creation.
`request_at`	Long	Unix timestamp (ms) when the request was first received.
`analyzed_at`	Long	Unix timestamp (ms) when the analysis process finished.
`transaction`	Object	The core analysis and financial data object.

2. Transaction Object

Parameter	Type	Description
`id`	String	Internal Rillis ID for this specific transaction.
`transaction_type`	Enum	`FIAT` or `CRYPTO`.
`state`	Enum	Status: `PROGRESS`, `COMPLETED`, `REJECTED`, `EVALUATION`.
`sending_dollar_amount`	Number	Equivalent value in USD at the time of the request.
`sending_amount`	Number	Amount sent in the source currency.
`sending_currency`	String	ISO Code or Asset symbol (e.g., "CLP", "BTC").
`receiving_wallet`	String	Destination address (for Crypto transactions).
`reasons_rejection_analysis`	String	Reason for rejection generated by the automated engine.
`reasons_rejection_operator`	String	Manual notes added by a compliance officer.
`rejected_at`	Long	Unix timestamp (ms) if the transaction was rejected.
`notification`	Object	Information about the Webhook delivery.

3. Notification Object

Parameter	Type	Description
`webhook`	String	The URL where the notification was sent.
`sent_at`	Long	Unix timestamp (ms) of the notification attempt.
`successful`	Boolean	`true` if your server responded with a 2xx status code.
`error`	String	Error message if the notification failed to deliver.

Full Response Example

{
    "items": [
        {
            "external_transaction_id": "your_external_transaction_id",
            "analyzed_at": 1770234049519,
            "request_at": 1770234048255,
            "transaction": {
                "transaction_type": "CRYPTO",
                "sending_dollar_amount": 100,
                "reasons_rejection_analysis": "Se rechazo el beneficiario por coincidencia en BlackList.",
                "reasons_rejection_operator": null,
                "rejected_at": 1770234049519,
                "analyzed_at": 1770234049519,
                "state": "EVALUATION",
                "notification": {
                    "webhook": "https://webhook.site/863cfb52-df2b-4b8d-b7cb-93ae4e8ba18f",
                    "sent_at": 1770234050418,
                    "successful": true,
                    "error": null
                },
                "id": "6983a0c061f1341eb94bd193",
                "crypto_asset": null,
                "sending_amount": 3424342,
                "sending_currency": "CLP",
                "crypto_network": null,
                "receving_amount": null,
                "receiving_currency": null,
                "receiving_wallet": "0x1d7e175a1fc32519d2d5591d69d996b60be21d3a"
            }
        },
        {
            "external_transaction_id": "your_external_transaction_id_two",
            "analyzed_at": 1770066522549,
            "request_at": 1770066521327,
            "transaction": {
                "transaction_type": "CRYPTO",
                "sending_dollar_amount": 600,
                "reasons_rejection_analysis": "Se rechazo el beneficiario por coincidencia en BlackList.",
                "reasons_rejection_operator": null,
                "rejected_at": 1770066522549,
                "analyzed_at": 1770066522549,
                "state": "EVALUATION",
                "notification": {
                    "webhook": "https://webhook.site/863cfb52-df2b-4b8d-b7cb-93ae4e8ba18f",
                    "sent_at": 1770066523436,
                    "successful": true,
                    "error": null
                },
                "id": "6981125961f1341eb94bcaae",
                "crypto_asset": null,
                "sending_amount": 3424342,
                "sending_currency": "CLP",
                "crypto_network": null,
                "receving_amount": null,
                "receiving_currency": null,
                "receiving_wallet": "0x1d7e175a1fc32519d2d5591d69d996b60be21d3a"
            }
        }
    ],
    "totalItems": 159,
    "page": 1,
    "totalPages": 16
}

Error Responses

In case of an error, the API will return an appropriate HTTP status code along with a JSON response containing error details:

Status Code	Description
400	Bad Request - The request was invalid or cannot be processed.
401	Unauthorized - Authentication credentials are missing or invalid.
403	Forbidden - The client does not have permission to access the requested resource.
404	Not Found - The requested transaction was not found.
429	Too Many Requests - The client has sent too many requests in a given amount of time.
500	Internal Server Error - An error occurred on the server.

Example Error Response

{
  "success": false,
  "error": "Transaction not found",
  "error_code": "RESOURCE_NOT_FOUND",
  "details": "No transaction found with the provided client_transaction_id"
}

Transaction Status Definitions

Status	Meaning	Recommended Action
PROGRESS	The AML/KYT analysis engine is currently processing the request.	Wait for the Webhook notification or poll again in 10-30 seconds.
COMPLETED	The screening is finished, and no significant risks or sanctions were detected.	Safe to proceed with the financial operation.
REJECTED	A high-risk match or a direct sanction hit was detected. The transaction is blocked.	Stop the operation immediately. Check the `reasons_rejection_analysis` field.
EVALUATION	A potential risk or "soft match" was found (e.g., possible match in a Blacklist).	Requires manual review. A Compliance Officer must approve or reject it in the Dashboard.

Rate Limits

Maximum of 200 requests per minute.

Maximum of 2,000 requests per hour.

Maximum of 20,000 requests per day.

Exceeding these limits will result in a 429 Too Many Requests response.

Monitoring & History

Request Parameters (Query Strings)#

1. Mandatory Authentication#

2. Search & Filtering#

Example Request (Single Transaction)#

Example Request (Multiple Transactions)#

Response#

Root Properties#

Item Object Details (The Analysis)#

2. Transaction Object#

3. Notification Object#

Full Response Example#

Error Responses#

Example Error Response#

Transaction Status Definitions#

Rate Limits#