Documentation Structure
2 min
\<font color="#78b5c7">\</font> topic type concept purpose explain the accertify api documentation structure audience api integrators and client developers applies to public accertify rest apis does not apply to internal batch processing or non‑request‑based integrations this documentation uses a structured approach to help you find the right information at the right time documentation sections the accertify api documentation is organized into five major sections getting started docid\ mff0kez4dg0xsdeld1tae orientation material that explains what the apis are and how to approach the documentation core concepts docid\ n8nqgm3c9vgdxudq54ktl shared mental models that apply across apis, such as how events, requests, and data objects are structured global constraints docid\ hxd7wt2raxtw6nh2h3yn0 rules and requirements that apply universally, including field level requirements and security constraints api groupings conceptual overviews that explain the purpose and scope of fraud apis docid 0ef2mhwfwcnjj1rnaspps , dispute apis docid\ hjxrd7 6jj3hd 5sftmi2 , and risk and intelligence apis docid\ k9byfhtyopizbktsh9tr0 separation of guidance and structure this documentation intentionally separates conceptual understanding from technical structure concept topics explain how to think about api behavior, events, and data relationships constraint topics define rules and requirements that must be followed reference topics describe exact api structures, schemas, and fields understanding this separation will help you navigate the documentation efficiently and avoid misinterpreting field‑level details without the appropriate context