RataHQ
Home Join Console

Approved consumer console

Act as your client.

After approval, use the credential file you downloaded when you applied. This console gives integration teams a guided path for sending claims, changing lifecycle state, reading a passport, and reviewing committed business actions.

Credential boundary: your seed is read from the file into page memory and never sent. Every request gets a fresh one-use EdDSA proof; lock forgets it immediately.

01 / Access

Unlock with your credential file

Choose the downloaded credential-<application>.json. Approval is checked against the live service before any action is enabled.

Parsed locally. The file is not uploaded; only signed request proofs cross the boundary.

02 / Overview

A clear path from proof to record

Start with a template, keep the advanced JSON when you need it, and hand a returned identifier to the next step only when the next form is still a clean draft.

Capture

Send one claim

Choose one of six examples or edit the full JSON. The idempotency key is fixed before signing.

Open claim composer

Change

Explain a lifecycle event

Correction does not take a replacement. Supersession does. The form checks that distinction before a request.

Open lifecycle

Inspect

Read every authorized signal

Passport responses stay complete, can be paged, copied, or downloaded, and never disappear into a short preview.

Open passport

Reconcile

Follow committed actions

History records successful business actions for your client. A lost write response is shown as unknown until reconciled.

Open history

03 / Submit claim

Capture a typed claim

Templates are starting points. The advanced editor remains the source of truth, so fields the service does not yet display survive your handoff.

Choosing a template replaces only this editor. A dirty editor asks first.

Guided fields (update the advanced JSON without dropping extra properties)

Unknown JSON properties remain in place. Clear a guided field only when the service contract allows the property to be absent.

The complete JSON object is sent as written. Unsupported properties remain intact.

An identifier you declare; it is stamped on this claim. A passport read must name the same grant, subject, purpose, recipient and period.

04 / Lifecycle

Record a lifecycle change

Use the guided fields for common transitions or open the event JSON and preserve the exact shape your integration owns.

Leave this blank to use the guided fields. Editing it sends your complete object and preserves extra properties.

05 / Passport

Read the complete authorized projection

A read only sees claims stamped with the bindings you name here — grant, subject, purpose, recipient and period must match the submitted claim. Use "Read this subject's passport" after committing a claim, or type the bindings yourself.

The identifier you stamped on the claims you want to read. Purpose maps to the claim's intended_use, recipient to its context_ref.

No projection loaded.

06 / History

Reconcile committed business actions

History is scoped to this client and records durable business outcomes. Reads, failed attempts, proofs, seeds, and claim payloads are never placed here.

History has not been loaded.