Skip to content

Read Fraud network contribution

GET
/v1/object-types/hospitality.fraud_network_contribution/objects/{id}
curl --request GET \
--url https://api.aerandil.com/v1/object-types/hospitality.fraud_network_contribution/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
--header 'Authorization: Bearer <token>'

Read an existing instance.

A confirmed fraud outcome this house offered to Watchtower, the card rail’s federated fraud network (proposal 0029): a dispute lost for fraud (chargeback_lost_fraud, the issuer’s word) or an assessment applied as a block on the house’s own evidence (confirmed_fraud, the house’s word — at another house it sends a hold to review, never blocks it, and it may not rest on the network’s own answer), carried as salted one-way fingerprints of the card, the guest’s email and phone. Only the digests reach the network, never the identifiers, never the booking; the network never tells another house which house contributed. Recorded by the card rail only, under the house’s fraud_network consent; withdraw_fraud_signal takes it back out (forward-only — answers already given stand), by the house or, on its review of a contested answer, by the platform on the house’s behalf (withdrawn_by). One per source (source_reference, the processor’s dispute id or the assessment id).

id
required
string format: uuid

Object id (UUID v7, server-generated at create time).

branch
string format: uuid

Read through an open branch’s copy-on-first-write overlay view instead of the canonical (main) plane. Does not compose with as_of (422). The branch must exist under the caller’s tenant.

Object found.

Media typeapplication/json
object
created_at
required
string format: date-time
id
required
string format: uuid
object_type
required
Allowed value: hospitality.fraud_network_contribution
properties
required
object
contributed_at
required
When the outcome was offered
string format: date-time
fingerprints
The digests offered, as `[{kind, digest}]` — `kind` one of card / email / phone, `digest` 64 lower-case hex (HMAC-SHA256 under the network salt). Never an identifier
id
required
Contribution id
string
outcome
required
The confirmed outcome contributed
string
Allowed values: chargeback_lost_fraud confirmed_fraud
salt_epoch
required
The network salt generation the digests were taken under
integer
source_reference
What the outcome was read from — the processor's dispute id or the assessment id; one contribution per source
string
status
required
Whether the contribution stands in the network
string
Allowed values: active withdrawn
withdrawal_reason
Why it was taken back, in words
string
withdrawn_at
When it was taken back out of the network
string format: date-time
withdrawn_by
Who took it back — the house, or the platform on its review of a contest, on the house's behalf. Absent on a withdrawal recorded before 2026-11-03, which was the house's
string
Allowed values: house platform
provenance

Per-property source attribution and pins. An entry under properties means the property’s current value came from that source (on the source’s own clock, source_updated_at); an entry under pins is a human override protecting the property from sourced writes.

object
pins
object
key
additional properties
object
pinned_at
string format: date-time
pinned_by
object
reason
required
string
properties
object
key
additional properties
object
external_id
string
recorded_at
required
string format: date-time
source
required
string
source_updated_at
string format: date-time
stream
string
scope
required
One of: discriminator: level
object
level
required
string
Allowed value: tenant
Allowed values: tenant
tenant_id
required
string format: uuid
updated_at
required
string format: date-time
version
required
integer
>= 1
Example
{
"object_type": "hospitality.fraud_network_contribution",
"properties": {
"outcome": "chargeback_lost_fraud",
"status": "active",
"withdrawn_by": "house"
},
"scope": {
"level": "tenant"
}
}
ETag
string
/^"\d+"$/

Quoted strong validator (RFC 7232 §2.3) carrying the object’s monotonic version. Informational on the read path — object mutation goes through typed actions on /v1/actions/{action}/apply, not raw CRUD.

No object with that id (or soft-deleted).