---
title: Documentation Structure
slug: public-apis/documentation-structure
createdAt: 2026-03-04T14:29:15.116Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose**: Explain the Accertify API documentation structure.

**Audience**: API integrators and client developers.&#x20;

**Applies to**: Public Accertify REST APIs.&#x20;

**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.&#x20;

## Documentation Sections

The Accertify API documentation is organized into the following major sections:

:::ExpandableHeading
### [Getting Started](docId\:Mff0KeZ4dG0xsDELd1tae)

Orientation material that explains what the APIs are and how to approach the documentation.&#x20;
:::

:::ExpandableHeading
### [Core Concepts](docId\:N8nqgM3c9VGdXuDq54ktl)

Shared mental models that apply across APIs, such as how events, requests, and data objects are structured.&#x20;
:::

:::ExpandableHeading
### [Global Constraints](docId\:Hxd7WT2raxTW6NH2h3YN0)

Rules and requirements that apply universally, including field-level requirements and security constraints.&#x20;
:::

:::ExpandableHeading
### API Groupings

- [Universal Fraud APIs](docId:0ef2mhWfWcNJj1rnAsPPS):&#x20;
  Conceptual overviews, industry guidance, and API references for the primary fraud API framework.
- [Dispute APIs](docId\:hjxRD7_6jj3HD-5sFtmI2):
  APIs used to support chargeback management and dispute workflows.
- [Risk and Intelligence APIs](docId\:K9BYFHtYOPIzbktsh9TR0):
  APIs used for account protection, investigation, intelligence, and data services.
- **Legacy APIs**:
  Documentation retained for existing implementations that have not yet migrated to Universal Fraud APIs.


:::

## 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.

## Current and Legacy Documentation

Universal Fraud APIs are the authoritative source for new fraud integrations. Legacy API documentation is maintained separately for customers supporting existing implementations.

When documentation exists in both locations, Universal Fraud API documentation should be treated as the primary source of implementation guidance.
