Source: https://docs.debitura.com/developer-concepts

# Developer Concepts

Cross-segment technical primitives for integrating with Debitura APIs.

-   **[Authentication](https://docs.debitura.com/developer-concepts/authentication.md)** — API key authentication
-   **[Environments](https://docs.debitura.com/developer-concepts/environments.md)** — Production and sandbox environments
-   **[Case Identifiers](https://docs.debitura.com/developer-concepts/case-identifiers.md)** — Reference numbers and unique identifiers
-   **[Claim Amount and Age](https://docs.debitura.com/developer-concepts/claim-amount-and-age.md)** — Three ways to provide claim principal and aging data
-   **[Error Handling](https://docs.debitura.com/developer-concepts/error-handling.md)** — Error formats and common codes
-   **[Pagination](https://docs.debitura.com/developer-concepts/pagination.md)** — Paginating list responses
-   **[Rate Limiting](https://docs.debitura.com/developer-concepts/rate-limiting.md)** — API rate limits and throttling
-   **[Idempotency](https://docs.debitura.com/developer-concepts/idempotency.md)** — Safe retry patterns
-   **[Filtering and Sorting](https://docs.debitura.com/developer-concepts/filtering-and-sorting.md)** — Query parameters for filtering and sorting
-   **[Webhooks](https://docs.debitura.com/developer-concepts/webhooks.md)** — Event notifications and signature verification
-   **[Case Lifecycle](https://docs.debitura.com/developer-concepts/case-lifecycle.md)** — How cases progress through collection
-   **[Engagement Phase](https://docs.debitura.com/developer-concepts/engagement-phase.md)** — Pre-legal, Legal, and Enforcement — a separate axis from case status
-   **[Tasks](https://docs.debitura.com/developer-concepts/tasks.md)** — Action items, solution URLs, and API-resolvable tasks
-   **[Test Cases](https://docs.debitura.com/developer-concepts/test-cases.md)** — Creating test data without triggering collection

These concepts apply across all integration tracks. For business logic and workflows, see the respective track documentation.
