Getting Started
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose introduce the apis and their role within the audience prospective clients, existing clients, and technical teams evaluating or implementing apis applies to all public facing apis does not apply to internal only services or non‑api integrations the apis provide programmatic access to key platform capabilities that support fraud risk assessment, dispute management, data privacy workflows, and data retrieval these apis enable clients to integrate services directly into their systems, allowing them to submit data, retrieve insights, and take action as part of their operational workflows each api is designed with a specific purpose, ranging from real‑time fraud evaluation and historical data analysis to chargeback management and privacy request handling while the apis address different use cases, they follow consistent design patterns and share common concepts, making integration predictable and scalable the apis are intended to provide insight, signals, and operational control , not to execute transactions or manage payment processing clients use these apis to inform decisions, automate responses, and integrate capabilities into their broader risk and operations ecosystems how apis are used apis are used to submit data to the , retrieve insights, and perform operational actions as part of a client’s workflow each api is designed around a specific use case—such as fraud risk evaluation, dispute management, data privacy requests, or data retrieval—and may operate synchronously or asynchronously depending on the api while each api has its own behavior and response patterns, they share consistent design principles and documentation structure to make integration predictable across products see also core concepts docid\ n8nqgm3c9vgdxudq54ktl how evaluates fraud risk across events, time, and customer behavior global constraints docid\ hxd7wt2raxtw6nh2h3yn0 authentication methods, hashing requirements, and other api parameters api reference page docid 40scz3hvgitth6c2i6jja field definitions and requirements for every api