Send First Transaction
Example ingestion request and what to expect from the evaluation response.
First ingestion milestone
The first successful transaction confirms that the tenant, key, payload, and decision path are working together.
Decision validation
A successful response should give you a usable risk result, not just a 200 status code.
Section
What this page is for
This page focuses on the single most important WatchTower integration event: the first successful transaction ingestion.
The goal is to prove that
- your API key works
- your request format is valid
- WatchTower can evaluate your payload
- the decisioning and operations layer can now be tested
Section
Endpoint and headers
Request target
POST /api/v1/transactions
x-api-key: wt_your_org_key
idempotency-key: <unique-value>
content-type: application/json
Section
Minimal useful payload
- transaction ID
- amount
- currency
- channel
- transaction type
- timestamp
- sender object
- receiver object
Payload strategy
Start with a minimal event, then add richer device and behavior context later.
Section
Expected result
- the ingestion request succeeded
- WatchTower returned a decision
- the transaction is visible in the console
- suspicious payloads can now be used to test alerts and cases
Section
If the request fails
- the API key is correct
- the idempotency key is present
- the payload is valid JSON
- required fields are included
- you are using the correct environment base URL
Operational note
Treat the first successful transaction as both an integration milestone and an operational-readiness check.
Next UpAuthentication
Continue Through The DocsWatchTower Integration Guides