# Title ## Docs - [🚀 Getting Started](https://docs.rillis.io/getting-started.md): - 🔎 Screening API [Overview](https://docs.rillis.io/overview-960147m0.md): - 🔎 Screening API [Blacklist Matching Logic](https://docs.rillis.io/blacklist-matching-logic-1862051m0.md): - 🌊 Flow API [Overview](https://docs.rillis.io/overview-935725m0.md): - 🌊 Flow API [Flow Step: Identity Verification](https://docs.rillis.io/api/identity-verification/identity-verification.md): - 🌊 Flow API [Flow Step: Onboarding Individual](https://docs.rillis.io/flow-step-onboarding-individual-1047643m0.md): - 🌊 Flow API [Flow Step: Onboarding Organization](https://docs.rillis.io/flow-step-onboarding-organization-1047649m0.md): - 🌊 Flow API > 📤 Webhooks [Webhooks Overview](https://docs.rillis.io/webhooks-overview-933481m0.md): - 🌊 Flow API > 📤 Webhooks [Flow](https://docs.rillis.io/flow-1051391m0.md): - 🌊 Flow API > 📤 Webhooks [Identity Verification](https://docs.rillis.io/identity-verification-1051374m0.md): - 🌊 Flow API > 📤 Webhooks [Onboarding Individual](https://docs.rillis.io/onboarding-individual-1017881m0.md): - 🌊 Flow API > 📤 Webhooks [Onboarding Organizations](https://docs.rillis.io/onboarding-organizations-1017886m0.md): - 🌊 Flow API > 📤 Webhooks [Identity Verification by Onboarding](https://docs.rillis.io/identity-verification-by-onboarding-1051397m0.md): - 💸 Transaction API [🔑 Authentication](https://docs.rillis.io/authentication.md): - 💸 Transaction API [Overview](https://docs.rillis.io/api/operations/operations-api.md): - 💸 Transaction API [Transaction Analysis](https://docs.rillis.io/api/operations/transaction-analysisi.md): - 💸 Transaction API [Transaction Status](https://docs.rillis.io/api/operations/transaction-status.md): - 💸 Transaction API [Document Types](https://docs.rillis.io/api/operations/document-types.md): - 💸 Transaction API [Cryptocurrencies](https://docs.rillis.io/api/operations/cryptocurrencies.md): - 💸 Transaction API [Diagram](https://docs.rillis.io/flow-diagram.md): - 💸 Transaction API [📤 Webhooks](https://docs.rillis.io/webhook.md): - 📂 Resources [Concept Details](https://docs.rillis.io/resources/concept-details.md): - 📂 Resources [Enum Validation](https://docs.rillis.io/resources/enum-validation.md): ## API Docs - 🔎 Screening API [Blockchain Analysis](https://docs.rillis.io/blockchain-analysis-15909043e0.md): This endpoint performs an in-depth risk analysis of a blockchain wallet based on its address and network. The response includes: - 🔎 Screening API [Individuals Analysis](https://docs.rillis.io/individuals-analysis-16165293e0.md): Screen an individual (name, DOB, nationality, etc.) against global watchlists and PEP lists. Results include risk level and matching records, with detailed profiles when available. - 🔎 Screening API [Organizations Analysis](https://docs.rillis.io/organizations-analysis-16165304e0.md): Screen a legal entity by name and country. The response includes matched entities, risk levels, and links to full profiles detailing ownership, sanctions, and regulatory concerns. - 🔎 Screening API [Screening Entities Summary Analysis](https://docs.rillis.io/screening-entities-summary-analysis-16165767e0.md): Retrieve a list or summary of previously analyzed individuals or entities, including current risk ratings and key metadata for dashboard or reporting use. - 🔎 Screening API [Create BlackList](https://docs.rillis.io/create-blacklist-23993550e0.md): This endpoint allows you to create and register a new blacklist entry within your Rillis account. Blacklist records are used during screening and compliance processes to identify wallets, individuals, or organizations that require special attention or risk evaluation. When a record is created, it becomes part of your internal blacklist, which is continuously used by Rillis to compare incoming screening inputs such as names, document numbers, countries, or wallet addresses. Any future analysis that matches this record will generate blacklist matches and influence the overall risk assessment. - 🔎 Screening API [Get All BlackList Records](https://docs.rillis.io/get-all-blacklist-records-25655235e0.md): Retrieve the complete list of blacklist records configured in your account. - 🔎 Screening API [Get Blacklist Record by ID](https://docs.rillis.io/get-blacklist-record-by-id-25655317e0.md): Fetch the full detail of a specific blacklist entry using its unique ID. Returns all associated data such as type, identification values, creation date, and current status. Ideal for reviewing specific matches or verifying why an entity was flagged. - 🔎 Screening API [Delete Blacklist Record by ID](https://docs.rillis.io/delete-blacklist-record-by-id-25657328e0.md): Permanently remove a blacklist record from your internal list. - 🔎 Screening API [Update Blacklist Record by ID](https://docs.rillis.io/update-blacklist-record-by-id-25657826e0.md): Modify the details or status of an existing blacklist entry. This allows you to adjust identifying fields, enable/disable the record, or apply changes based on new information without deleting the entry. - 🔎 Screening API [Update Blacklist Settings Account](https://docs.rillis.io/update-blacklist-settings-account-25657991e0.md): Manage the global configuration of your blacklist behavior. - 🌊 Flow API > 📡 Endpoints [Authentication token](https://docs.rillis.io/authentication-token-15782106e0.md): This endpoint generates an **access token** that is required to authenticate all subsequent API requests in the Flow API. - 🌊 Flow API > 📡 Endpoints [Get Flow Instance](https://docs.rillis.io/get-flow-instance-15816126e0.md): Fetch results of a flow instance, which is the complete record of user-provided answers and all associated data within the system. - 🌊 Flow API > 📡 Endpoints [Get File from Flow Instance](https://docs.rillis.io/get-file-from-flow-instance-15816281e0.md): To obtain one file associated with a flow instance. - 🌊 Flow API > 📡 Endpoints [Identity: Get Details](https://docs.rillis.io/identity-get-details-15784633e0.md): Retrieves the complete identity verification details for a specific verification instance within a flow. - 🌊 Flow API > 📡 Endpoints [Identity: Get Files](https://docs.rillis.io/identity-get-files-15784709e0.md): Allows you to retrieve a list of files associated with a specific identity verification process. This endpoint returns detailed information for each file, including metadata such as the original name, file type, size, path, and a Base64-encoded representation of the file content. This data can be used for validation, storage, or display purposes. - 🌊 Flow API > 📡 Endpoints [Identity: Update Status](https://docs.rillis.io/identity-update-status-15784669e0.md): Updates the status of a specific identity verification step within a flow. - 🌊 Flow API > 📡 Endpoints [Onboarding: Get Details](https://docs.rillis.io/onboarding-get-details-15784728e0.md): Allows you to retrieve the details of an onboarding process, whether for an individual or a company. This endpoint provides comprehensive information about the onboarding step, which is a specific stage within an onboarding flow. The request requires an identifier (id) to locate the onboarding record. The response includes a detailed object with all the relevant data for that onboarding instance, enabling you to manage, validate, or display the onboarding status and related details. - 🌊 Flow API > 📡 Endpoints [Onboarding: Get File](https://docs.rillis.io/onboarding-get-file-15784796e0.md): Retrieves a single file associated with the onboarding process. This endpoint allows you to access the file by specifying its identifier (file_id). It returns all the details of the file, including its name, encoding, MIME type, size, path, and a base64-encoded content for direct access. - 🌊 Flow API > 📡 Endpoints [Onboarding: Get Multiple Files](https://docs.rillis.io/onboarding-get-multiple-files-15815899e0.md): Retrieves a collection of files associated with a specific process. This endpoint returns an array containing metadata for each file, such as the file identifier (id), original name, encoding, MIME type, size, storage path, and a base64-encoded string representing the file content. This enables you to access and handle multiple files efficiently. - 🌊 Flow API > 📡 Endpoints [Onboarding: Update Status](https://docs.rillis.io/onboarding-update-status-15813460e0.md): To manually update the status of the onboarding step. - 📡 Endpoints [Create operation](https://docs.rillis.io/create-operation-15490183e0.md): This endpoint submits a transaction for analysis. Once registered, RILLIS stores and processes the transaction (analysis may take around 30 seconds). Be sure to include the required authentication credentials in the request body. - 📡 Endpoints [Get operation](https://docs.rillis.io/get-operation-15490185e0.md): This endpoint retrieves the current status of transactions. Provide a client_transaction_id to query a specific transaction, or leave it out to return the latest 10 transactions by default. Pagination is supported using the limit and page parameters. - 📡 Endpoints [Get valid document types](https://docs.rillis.io/get-valid-document-types-15490187e0.md): This endpoint returns the valid document types by country, supporting two categories: individuals ("person") and legal entities ("company"). - 📡 Endpoints [Get valid coins](https://docs.rillis.io/get-valid-coins-15490188e0.md): This endpoint returns a list of available cryptocurrencies, ensuring that the selected network corresponds to a valid asset.