Docs menu

Referrals API endpoint

List referral attributions

Lists referral attributions with their reward records for support and operational review.

GETadmin or apiKey1 credit/requestReferralsreferrals.adminReferralsListResponseDoc/admin/referrals

Overview

Lists referral attributions with their reward records for support and operational review.

Request schema

NameInTypeRequiredEnumExampleDescription
x-api-keyheaderstringYesAdmin API key
user_idquerystringNoFilter by referrer or referred user id
statusquerystringNoattributed, qualified, review_required, rewarded, expired, capped, failed, rejectedFilter by attribution status
campaignquerystringNoFilter by UTM campaign
pending_grantquerybooleanNoOnly attributions with pending reward grants
limitqueryintegerNoMaximum records to return, capped at 100

Authentication

Admin endpoints require an Admin JWT through the console proxy or an Admin API key where documented. Non-admin plans receive 403.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost
1 credit/request
Charged response
Successful 2xx responses
PlanPriceIncluded creditsDaily capRate limitOverage
Free$0/mo2,000500 daily credits5/minNo overage
Starter$9/mo20,0005,000 daily credits15/min$0.75/1,000 overage credits when enabled
Growth$29/mo100,00025,000 daily credits45/min$0.45/1,000 overage credits when enabled
Pro$79/mo400,000No daily cap120/min$0.30/1,000 overage credits
Business$199/mo1,200,000No daily cap300/min$0.20/1,000 overage credits
Enterprise$499/mo5,000,000No daily cap1,000/min$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

  • Proxy strategy: managed automatically where needed
  • Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
  • Browser cluster: supported dynamic workloads can be routed through distributed browser instances
  • Retry behavior: automatic retry/fallback may be used depending on endpoint type
  • Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
  • Billing: credits are charged only for successful 2xx responses
  • Observability: responses include request context where available

Response behavior

- Returns attribution records with raw user ids for Admin review. - Includes reward records for each attribution so pending or failed credit grants are visible. - Does not mutate referral state.

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

StatusCommon failure case
400Invalid input or missing required parameter
429Plan or endpoint rate limit exceeded
500Internal execution error
502Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

StatusDescriptionSchema
401Authentication required#/definitions/app.Response
403Admin plan required#/definitions/app.Response
500Internal server error#/definitions/app.Response

Example response

{
  "code": 200,
  "msg": "ok",
  "data": {
    "items": [
      {
        "attribution": {
          "id": "attr-1",
          "code": "A1B2C3D4E5F6",
          "referrer_user_id": "user-referrer",
          "referred_user_id": "user-referred",
          "status": "rewarded"
        },
        "rewards": [
          {
            "id": "reward-1",
            "role": "referrer",
            "credits": 10000
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/referrals.adminReferralsListResponseDoc

FieldTypeRequiredEnumBoundsExampleDescription
itemsarrayNo
items[].attributionreferrals.adminReferralAttributionRecordDocNo
items[].attribution.click_idstringNorefclk_abc123
items[].attribution.codestringNoA1B2C3D4E5F6
items[].attribution.created_atstringNo
items[].attribution.errorstringNotemporary billing write failure
items[].attribution.expires_atstringNo
items[].attribution.first_paid_invoice_idstringNoin_123
items[].attribution.idstringNoattr-1
items[].attribution.landing_pathstringNo/pricing
items[].attribution.qualified_atstringNo
items[].attribution.referred_user_idstringNouser-referred
items[].attribution.referrer_user_idstringNouser-referrer
items[].attribution.review_reasonstringNosame_stripe_customer
items[].attribution.reviewed_atstringNo
items[].attribution.reviewed_bystringNoadmin-user
items[].attribution.rewarded_atstringNo
items[].attribution.risk_flagsarrayNosame_stripe_customer
items[].attribution.skip_reasonstringNocapped
items[].attribution.statusstringNoattributed, qualified, review_required, rewarded, expired, capped, failed, rejectedrewarded
items[].attribution.stripe_event_idstringNoevt_123
items[].attribution.stripe_invoice_idstringNoin_123
items[].attribution.utm_campaignstringNospring-launch
items[].attribution.utm_mediumstringNoemail
items[].attribution.utm_sourcestringNonewsletter
items[].rewardsarrayNo
items[].rewards[].attribution_idstringNoattr-1
items[].rewards[].created_atstringNo
items[].rewards[].creditsintegerNo10000
items[].rewards[].credits_grant_errorstringNotemporary billing write failure
items[].rewards[].credits_grant_keystringNoreward-1
items[].rewards[].credits_granted_atstringNo
items[].rewards[].idstringNoreward-1
items[].rewards[].rolestringNoreferrer, referredreferrer
items[].rewards[].stripe_invoice_idstringNoin_123
items[].rewards[].user_idstringNouser-referrer

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/admin/referrals?status=attributed&pending_grant=true&limit=10" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

Related