Skip to content
aerandil.com
GitHub

Validate Record federated contribution (dry-run)

POST
/v1/actions/hospitality.action.record_federated_contribution/validate
curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.record_federated_contribution/validate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "attestation_reference": "example", "clipping_applied": true, "contribution_kind": "encrypted_aggregate", "contribution_slot": "example", "delta_spent": "example", "epsilon_spent": "example", "input_snapshot_hash": "example", "input_window_end": "2026-04-15T12:00:00Z", "input_window_start": "2026-04-15T12:00:00Z", "local_code_digest": "example", "local_record_count_bucket": "lt_10", "local_runner_version": "example", "local_subject_count_bucket": "lt_10", "participation_id": "example", "payload_hash": "example", "payload_reference": "example", "payload_size_bytes": 1, "rejection_reason": "example", "result_status": "accepted", "secure_aggregation_mask_ref": "example", "validation_warnings": [ "example" ] }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.federated_run" } }'

Dry-run of apply_hospitality_action_record_federated_contribution’s parameter checks. No side effects, no idempotency reservation, no handler dispatch — just the schema pass plus action-level shape (target presence, target type, unknown-parameter rejection). return_modified is meaningless here and ignored.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
branch

Apply against an open branch’s overlay view instead of the canonical (main) plane. The action’s writes land in the branch’s copy-on-first-write overlay, its events in the branch’s own stream, and the invocation is journaled for merge-by-replay. Branch writes are action-only, so this is the write-side entry point to a branch (POST /v1/branches forks one).

string format: uuid
params
required
object
attestation_reference
TEE / runner attestation if used
string
clipping_applied
required
Required true for model updates
boolean
contribution_kind
required
Contribution kind
string
Allowed values: encrypted_aggregate noisy_aggregate model_update metrics_only attestation_only
contribution_slot
Slot discriminator when definition declares multiple slots
string
delta_spent
Local DP spend
string format: decimal
epsilon_spent
Local DP spend
string format: decimal
input_snapshot_hash
required
Hash over local eligible input snapshot metadata
string
input_window_end
required
Must match run
string format: date-time
input_window_start
required
Must match run
string format: date-time
local_code_digest
required
Must match approved definition unless override recorded
string
local_record_count_bucket
required
Bucketed record count
string
Allowed values: lt_10 10_49 50_99 100_499 500_999 1000_plus
local_runner_version
required
Runner or agent version
string
local_subject_count_bucket
Required for person-affecting definitions
string
Allowed values: lt_10 10_49 50_99 100_499 500_999 1000_plus
participation_id
required
Participation id
string
payload_hash
Required when payload_reference is set
string
payload_reference
Encrypted payload / clean-room output / secure aggregation share ref
string
payload_size_bytes
Safety bound
integer
rejection_reason
Bounded; required for rejected / suppressed
string
result_status
required
accepted | rejected | suppressed
string
Allowed values: accepted rejected suppressed
secure_aggregation_mask_ref
Optional protocol metadata
string
validation_warnings
Local runner warnings
Array<string>
return_modified

When true, the response carries modified_objects and modified_links projections — the engine reads the event log inside the same transaction so the projection observes the handler’s own writes.

boolean
target
required
object
id
required
string format: uuid
object_type
required
Allowed value: hospitality.federated_run

Responses

Section titled “Responses”

200

Section titled “200”

Validation outcome. result is valid or invalid; per-parameter diagnostics are always populated for every declared parameter so a UI can render the action’s full surface.

Media typeapplication/json
object
action
required
string
errors

Action-level errors not tied to a single parameter (missing target, target type mismatch, unknown parameter names). Absent when empty.

Array<string>
parameters
required

Per-parameter diagnostics keyed by api_name.

object
key
additional properties
object
errors
Array<string>
result
required
Allowed values: valid invalid
value
required

The serialised value the server interpreted, or null if the parameter was not supplied.

result
required
Allowed values: valid invalid
Example
{
  "parameters": {
    "additionalProperty": {
      "result": "valid"
    }
  },
  "result": "valid"
}