Solidgate Reporting provides two API approaches for retrieving report data. Choose the one that fits your integration, then follow the relevant guide to learn how to authenticate requests, retrieve reports, and manage report processing and expiration.
Report-specific pages describe the available fields and filters.
Dedicated endpoint for each
Guide
Export API v1 reports for a selected date range covering card and APM orders, subscriptions, chargebacks, PayPal disputes, prevention alerts, card fraud alerts, financial entries, and routing events.
report type
on reports.solidgate.com.
Returns paginated JSON for the requested date range. Most reports are synchronous.
Shared
reports API
API v2
at api.solidgate.com/v2.
Creates asynchronous CSV reports selected by report_type. Use account or channel-bound keys to authenticate.
Includes reports
Approaches
| Area | API v1 | API v2 |
|---|---|---|
| Authentication | merchant and signature headers. Requests are signed using HMAC-SHA512 with channel keys created for access to API. | Authorization: Bearer header with account- or channel-bound keys created for access to API. Requests do not require a signature. |
| Endpoint and format | Dedicated endpoint per report. Returns paginated JSON. | Shared Reports API. Returns CSV files. Select the report type with report_type. |
| Processing | Synchronous for most reports. Prevention alerts, financial entries, and routing events require asynchronous generation, polling, and download. | Asynchronous for all reports. Create the report, check its status, and download it when ready. |
| Request flow | Call the relevant
Guide
Export API v1 reports for a selected date range covering card and APM orders, subscriptions, chargebacks, PayPal disputes, prevention alerts, card fraud alerts, financial entries, and routing events. report endpoint with date_from, date_to, and optional filters or pagination parameters. |
Guide
Create, track, and download API v2 CSV reports by report type and date range with Bearer authentication. Create, check status, list, and download reports. |
| Date range | Defaults and date fields vary by report, such as created_at or updated_at. | Uses the date field for the selected report type, such as the creation or processing date. date_from is inclusive, date_to is exclusive. |
| Report expiration | Most reports do not expire. Prevention alerts, financial entries, and routing events expire 30 days after generation. | Reports expire 30 days after creation. |