Skip to main content
The endpoint you’ll use most. Returns a signed JSON document with the user’s standing tier, score, behavioural signals, and an aggregated view of their audit ledger over the consented window.

Fetch a snapshot

Path parameters

string
required
The Guild user ID. ULID, prefixed usr_.

Query parameters

integer
default:"consent_default"
Override the ledger window for this read. Must be ≤ the maximum permitted by the consent. Valid values: 30, 60, 90, 365.

Required headers

string
required
Bearer <api_key>. See Authentication.
The active consent ID for this user. ULID, prefixed cnst_.

Example

Response 200

string
User identifier.
string
One of JOB_SEEKER, TRADER, EMPLOYER.
string
One of Building, Emerging, Trusted, Established.
integer
Raw score 0-1000 behind the tier classification.
object
object
object
object
object
Only present if the consent includes the repayment_history scope.
string
ISO-8601 of when this snapshot was signed.
string
Ed25519 signature in the format ed25519:<base64>. See verification guidance.

Example response

Verifying the signature

Pull the public keys at GET /partner/v1/keys (cache up to 4 hours). The signature header includes a kid reference; match it to the public key with the same kid. Verification procedure:
1

Remove the signature field

The signature was computed over the payload without itself.
2

Canonicalise the JSON

Sort keys lexicographically at every level. Serialise with no extra whitespace.
3

Verify

Standard Ed25519 verification of the canonical bytes against the public key.
Reference implementations in Python, Node.js, and Go are available on the Partner Portal under “Resources.”

Error cases

Get the public keys

Returns the current set of public keys for signature verification. Rotated quarterly with a 30-day overlap window.

Response

Cache the response client-side. Don’t fetch per snapshot.

Consent links

How to ask a user for consent before fetching their snapshot.

Disbursements

Disbursing approved credit over OPay payout.