Yes. RChilli maintains audit logs that provide visibility into API activity, including the API invoked, the time of the API call, and the scoring configuration applied to the operation. RChilli My Account also provides activity and logging visibility along with configuration-management information for API usage.
There is an important scope limitation. Optional Search & Match features enabled dynamically within an individual request are not currently captured as separate feature-by-feature audit fields. While the applicable scoring configuration and default feature/configuration behavior can be reviewed by contacting RChilli Support, the complete set of request-level feature toggles is not currently preserved as a dedicated immutable configuration snapshot.
For end-to-end auditability where the recruiter's identity or user activity must also be recorded, the consuming ATS or recruitment platform should correlate its recruiter/user activity records with the corresponding RChilli API transaction.
Therefore, combining RChilli API-level logs with ATS user-level audit logs provides the most complete traceability of the matching activity.
Relevant Help Documents:
For more information, contact RChilli Support.
Comments
0 comments
Please sign in to leave a comment.