> ## Documentation Index
> Fetch the complete documentation index at: https://holder.docs.fiskil.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How to test and validate your Fiskil Data Provider integration before going live.

Before moving to production, every integration must be **tested and validated**.
Fiskil provides tools to help you check both **functional correctness** (your Resource Server works as expected) and **compliance alignment** (if a regulatory framework applies).

***

## What You Can Test

* **Authorization flows** — confirm that users can successfully grant and revoke consent.
* **Token validation** — check that your Resource Server enforces JWT signatures.
* **API responses** — validate your endpoints return the correct data, error formats, and pagination.
* **Performance** — measure latency and throughput to confirm baseline SLAs.
* **Compliance (optional)** — run against formal test suites if building under CDR, FDX, or similar frameworks.

***

## Core Tools

### Postman Collection

Run an end-to-end flow using Fiskil’s official Postman collection:

* Create consents
* Retrieve tokens
* Call your Resource Server endpoints
* Inspect responses

### Mock Data Recipient

Fiskil maintains a CDR Mock Data Recipient you can use to simulate CDR Consent flows:

* Create consents
* Browse consumer data
* Revoke consents

***

### Request Logs

Every API call is recorded in [Request Logs](/docs/telemetry/logs).

* Validate payloads, scopes, and status codes.
* Debug errors by tracing failed requests.
* Confirm traffic flows only within the granted consent.

***

### Metrics

Each instance tracks performance and availability metrics.

* Verify throughput and latency under load.
* Check baseline error rates before go-live.

See: [Metrics](/docs/telemetry/metrics)

***

### Compliance Tools

If your instance uses a **compliance profile** (e.g., CDR, FDX), Fiskil provides access to compliance validation tools.

* Run automated checks against required endpoints and scopes.
* Generate reports for regulators or internal audit.

<Note>
  For regulated environments, additional testing tools may be required.
  Please [contact the Fiskil team](https://fiskil.com/contact) to enable compliance testing support for your instance.
</Note>

See: [Compliance Tools](/docs/testing/compliance-tools)

***

## Environments

Always test thoroughly in **staging** before promoting to **production**:

* Staging allows mock recipients and relaxed change controls.
* Production must remain stable and audit-ready.

***

## Related

* [Using Postman](/docs/testing/postman)
* [Request Logs](/docs/telemetry/logs)
* [Metrics](/docs/telemetry/metrics)
* [Compliance Tools](/docs/testing/compliance-tools)