Skip to documentation content
Docs

GoWaly API

Developer docs

Integrate the GoWaly Verification API to analyze recipient risk and the Reporting API to submit structured fraud reports for moderation.

Overview

GoWaly Verification and Reporting machine APIs for server-to-server integrations.

Five partner operations #

MethodPathScope
POST/api/v1/check-recipientverification:read
POST/api/v1/reportsreports:write
GET/api/v1/reports/{report_id}reports:write
POST/api/v1/reports/{report_id}/evidencereports:write
POST/api/v1/reports/{report_id}/evidence/{evidence_id}/confirmreports:write

The technical API hostnames remain scamrader.com. GoWaly does not execute or authorize transfers; use its risk insight in your own decision policy.

Start here #

  1. Use Customer Sandbox for synthetic Verification testing. Its approved Verification fixtures are deterministic.
  2. Keep your API key on a server and send it in the Authorization header.
  3. Read the Verification and Reporting contracts, including error, quota, and retry rules.

Quickstart

Canonical contract #

The backend owns the Commercial OpenAPI artifact. The broader backend OpenAPI is not the partner integration contract.

Production Commercial OpenAPI

Staging review Commercial OpenAPI