CRISP partnersEndpoint reference

Get referral claim

GET /v1/accounts/{externalUserId}/referral-claims/{claimId}

Use this operation for get referral claim. Follow the referrals and rewards guide for the complete workflow.

Referrals and rewards guide · All endpoints · SDK: getReferralClaim, waitForClaim

Authentication

Server-to-server HMAC. Your key selects the partner; your backend must authorize the end user.

CRISP enables access to the features agreed for your integration. Contact CRISP if an enabled feature returns an access error.

Idempotency-Key: Not required by this operation. Signing and authentication →

Request fields

Required means the field must be present. Nullable means an explicit JSON null is allowed; it does not mean optional.

Path parameters

FieldType / presenceDescription and constraints
externalUserIdstring
Required
Non-null

Your stable user ID within the authenticated partner. Derive it from your authorized server session.

Validation pattern^[A-Za-z0-9._:@-]{1,200}$
claimIdstring
Required
Non-null
Format: uuid

Query parameters

None.

Header parameters

No operation-specific headers. The HMAC headers above still apply.

JSON body

No request body.

Request example

Illustrative identifiers only: replace them with resources from your integration. Keep credentials on your backend. HTTP placeholders must be signed; the SDK signs automatically. Financial intent keys must be persisted and unique per new action.

GET /v1/accounts/user-123/referral-claims/11111111-1111-4111-8111-111111111111
Host: partner-api.crisp.trade
X-Crisp-Partner-Key: <server-key-id>
X-Crisp-Timestamp: <fresh-ISO-8601-UTC-timestamp>
X-Crisp-Nonce: <fresh-unique-nonce>
X-Crisp-Signature: <computed-base64-HMAC>

Response fields

HTTP responses use the envelope below. SDK calls expose its payload as result.data, with HTTP status and request metadata on the SDK wrapper.

200 · Success

Data payload

FieldType / presenceDescription and constraints
claimobject
Required
Non-null
Expand the structure below.
claim: expand fields
FieldType / presenceDescription and constraints
idstring
Required
Non-null
Format: uuid
statestring
Required
Non-null
Allowed: "queued", "submitting", "submitted", "settled", "manual_review"
amountUsdcstring
Required
Non-null

Exact decimal string. Never use floating point for ledger arithmetic.

Validation pattern^\d+(?:\.\d+)?$
transactionHashstring | null
Required
Nullable
Expand the structure below.
transactionHash: expand fields

string

terminalboolean
Required
Non-null

Whether execution has reached a terminal state; inspect state to distinguish success from failure.

needsReviewboolean
Required
Non-null
—
createdAtstring
Required
Non-null
Format: date-time
updatedAtstring
Required
Non-null
Format: date-time

Additional fields are not allowed in this object.

Additional fields are not allowed in this object.

Full HTTP envelope
FieldType / presenceDescription and constraints
dataobject
Required
Non-null
Expand the structure below.
data: expand fields
FieldType / presenceDescription and constraints
claimobject
Required
Non-null
Expand the structure below.
claim: expand fields
FieldType / presenceDescription and constraints
idstring
Required
Non-null
Format: uuid
statestring
Required
Non-null
Allowed: "queued", "submitting", "submitted", "settled", "manual_review"
amountUsdcstring
Required
Non-null

Exact decimal string. Never use floating point for ledger arithmetic.

Validation pattern^\d+(?:\.\d+)?$
transactionHashstring | null
Required
Nullable
Expand the structure below.
transactionHash: expand fields

string

terminalboolean
Required
Non-null

Whether execution has reached a terminal state; inspect state to distinguish success from failure.

needsReviewboolean
Required
Non-null
—
createdAtstring
Required
Non-null
Format: date-time
updatedAtstring
Required
Non-null
Format: date-time

Additional fields are not allowed in this object.

Additional fields are not allowed in this object.

requestIdstring
Required
Non-null

Request correlation ID for debugging and support.

Additional fields are not allowed in this object.

Response example

Schema illustration, not live account data. Null means unavailable or not applicable, never an invented zero. Empty arrays do not imply the endpoint always returns no results.

200 response JSON
{
  "data": {
    "claim": {
      "id": "11111111-1111-4111-8111-111111111111",
      "state": "queued",
      "amountUsdc": "0.40",
      "transactionHash": null,
      "terminal": false,
      "needsReview": false,
      "createdAt": "2026-09-01T00:00:00Z",
      "updatedAt": "2026-09-01T00:00:00Z"
    }
  },
  "requestId": "example-request-id"
}

Errors and recovery

StatusMeaning
400Inspect error.code and retain the original financial intent.
401Inspect error.code and retain the original financial intent.
403Inspect error.code and retain the original financial intent.
404Not visible for this account. A recovery lookup miss is not proof that an in-flight submission failed.
409Inspect error.code and retain the original financial intent.
429Inspect error.code and retain the original financial intent.
500Inspect error.code and retain the original financial intent.
502Inspect error.code and retain the original financial intent.
503Inspect error.code and retain the original financial intent.

Inspect the error code and outcomeUnknown, not just the HTTP status. Preserve the original intent after financial uncertainty. Read-only retries should honor Retry-After. Recovery workflow →

Error response fields
FieldType / presenceDescription and constraints
errorobject
Required
Non-null
Expand the structure below.
error: expand fields
FieldType / presenceDescription and constraints
codestring
Required
Non-null
—
messagestring
Required
Non-null
—
requestIdstring
Required
Non-null

Request correlation ID for debugging and support.

Additional fields are not allowed in this object.

Additional fields are not allowed in this object.

Raw contract

OpenAPI download · Advanced schema and legacy anchor

CRISP Partner Documentation