Verification Report API (/verificationReport)

The Verification Report API allows you to retrieve verification information for LinkedIn members, including verification categories (e.g., IDENTITY, WORKPLACE), detailed metadata, and verification URLs for eligible members.

Overview

Key Features:

• Check member's verification status (identity and workplace)
• Get detailed verification metadata (Plus tier only)
• Generate verification URLs for unverified members
• OAuth: 3-legged (member consent required)
• Version: 202510 (Plus tier) / Check Release Notes (Dev/Lite tier)

Verification Categories

Rate Limits

Endpoint Details

GET https://api.linkedin.com/rest/verificationReport

Required Headers

Required OAuth Scope

Query Parameters

Examples:

# Request both verifications
GET /verificationReport?verificationCriteria=IDENTITY&verificationCriteria=WORKPLACE

# Request only identity
GET /verificationReport?verificationCriteria=IDENTITY

# No criteria (returns URL for any eligible verification)
GET /verificationReport

Response Fields by Tier

Common Fields (All Tiers)

These fields are available in Development, Lite, and Plus tiers:

Development & Lite Tier Response

Development and Lite tiers receive only the basic verification categories without detailed metadata.

Plus Tier Additional Fields

verifiedDetails Array (Plus Only)

Each object represents a completed verification with detailed metadata.

Common Fields:

IDENTITY Verification Fields:

WORKPLACE Verification Fields:

Example Requests and Responses

Example 1: Development/Lite Tier - Fully Verified Member

Member has completed both verifications. No verificationUrl in response.

Request:

curl -X GET 'https://api.linkedin.com/rest/verificationReport' \
  -H 'Authorization: Bearer {ACCESS_TOKEN}' \
  -H 'LinkedIn-Version: {LATEST_VERSION}'

Response (Development/Lite Tier):

{
  "verifications": ["IDENTITY", "WORKPLACE"],
  "id": "Yw-zU_kyua"
}

Try the /verificationReport API in Postman to explore verification states and metadata.

Example 2: Development/Lite Tier - Unverified Member

Member has no verifications but is eligible. Response includes verificationUrl.

Request:

curl -X GET 'https://api.linkedin.com/rest/verificationReport?verificationCriteria=IDENTITY&verificationCriteria=WORKPLACE' \
  -H 'Authorization: Bearer {ACCESS_TOKEN}' \
  -H 'LinkedIn-Version: {LATEST_VERSION}'

Response (Development/Lite Tier):

{
  "verifications": [],
  "id": "Yw-zU_kyua",
  "verificationUrl": "https://www.linkedin.com/trust/verification?isDeeplinkToCCT=true&verificationUrl=..."
}

Example 3: Plus Tier - Fully Verified Member with Metadata

Member has completed both verifications. Plus tier includes detailed metadata.

Request:

curl -X GET 'https://api.linkedin.com/rest/verificationReport' \
  -H 'Authorization: Bearer {ACCESS_TOKEN}' \
  -H 'LinkedIn-Version: 202510'

Response (Plus Tier with Detailed Metadata):

{
  "id": "zy5ubopzH4",
  "userId": "UfBk1351j0zQTGeF9TT3JCeztYB8CTz6INgveqjzg8g=",
  "lastRefreshedAt": 1761504023786,
  "verifications": ["IDENTITY", "WORKPLACE"],
  "verifiedDetails": [
    {
      "category": "IDENTITY",
      "verifiedName": {
        "firstName": "MICHAEL",
        "middleName": "GARY",
        "lastName": "SCOTT"
      },
      "lastVerifiedAt": 1744141828585
    },
    {
      "category": "WORKPLACE",
      "verificationMethod": "EMAIL_ADDRESS",
      "organizationInfo": {
        "name": "LinkedIn",
        "url": "https://www.linkedin.com/company/1337"
      },
      "lastVerifiedAt": 1744139009883
    }
  ]
}

Example 4: Plus Tier - Partially Verified Member

Member has identity verification, eligible for workplace. URL provided for workplace verification.

Request:

curl -X GET 'https://api.linkedin.com/rest/verificationReport?verificationCriteria=WORKPLACE' \
  -H 'Authorization: Bearer {ACCESS_TOKEN}' \
  -H 'LinkedIn-Version: 202510'

Response (Plus Tier):

{
  "id": "zy5ubopzH4",
  "userId": "UfBk1351j0zQTGeF9TT3JCeztYB8CTz6INgveqjzg8g=",
  "lastRefreshedAt": 1761504023786,
  "verifications": ["IDENTITY"],
  "verifiedDetails": [
    {
      "category": "IDENTITY",
      "verifiedName": {
        "firstName": "MICHAEL",
        "middleName": "GARY",
        "lastName": "SCOTT"
      },
      "lastVerifiedAt": 1744141828585
    }
  ],
  "verificationUrl": "https://www.linkedin.com/trust/verification?isDeeplinkToCCT=true&verificationUrl=...WORKPLACE..."
}

Understanding Verification States

Verification URL Usage

What is verificationUrl?

The verificationUrl field is a LinkedIn URL that directs members to complete verification on LinkedIn.

When it's present:

• Member is eligible for additional verifications
• If verificationCriteria specified: eligible for those specific verifications
• If no criteria: eligible for any verification type

When it's absent:

• Member has completed all requested verifications, OR
• Member is not eligible for any additional verifications

Using Redirect URI (Optional)

A redirect URI (callback URL) allows LinkedIn to return the member to your application after verification.

Flow:

1. Your app redirects member to the verification URL
2. Member completes verification on LinkedIn
3. LinkedIn redirects member back to your redirect URI
4. Your app resumes the member's session

Configuration Requirements:

Registration Steps:

1. Go to LinkedIn Developer Portal
2. Select your application → Auth tab
3. Under Authorized redirect URLs, add your redirect URI
4. Save changes

Implementation:

// Get verification URL from API response
const verificationUrl = apiResponse.verificationUrl;

// Add your redirect URI (must be URL-encoded)
const redirectUri = encodeURIComponent('https://yourapp.com/verification/callback');
const fullUrl = `${verificationUrl}&redirectUri=${redirectUri}`;

// Optionally add state parameter for CSRF protection
const state = generateRandomState(); // Store this in your database
const finalUrl = `${fullUrl}&state=${state}`;

// Redirect member to LinkedIn
window.location.href = finalUrl;

Handling Member's Return:

// In your callback handler at /verification/callback
app.get('/verification/callback', async (req, res) => {
  const { state, error } = req.query;
  
  // Validate state parameter
  if (state && !validateState(state)) {
    return res.status(400).send('Invalid state');
  }
  
  // Check for errors
  if (error) {
    return res.redirect('/dashboard?message=verification_cancelled');
  }
  
  // Fetch updated verification data
  const verificationData = await callVerificationReportAPI(accessToken);
  
  // Update your database
  await updateMemberVerification(memberId, verificationData);
  
  // Redirect to success page
  res.redirect('/dashboard?message=verification_complete');
});

Common Issues:

Important Concepts

Verified Name vs LinkedIn Profile Name (Plus Tier)

• The verifiedName in identity verification is the legal name from government ID
• LinkedIn Profile Name comes from /identityMe API (e.g., "John Doe")
• Verified Name comes from /verificationReport API (e.g., "JOHN M DOE")
• These names may differ intentionally

Data Freshness

All Tiers:

• Check verification status before critical actions (payments, access grants)
• Consider caching responses temporarily to reduce API calls

Plus Tier:

• Use lastRefreshedAt timestamp to determine when to refresh
• Recommended refresh frequency: once per day for most use cases
• Use /validationStatus API for bulk data freshness checks
• See Data Freshness Guide for comprehensive strategies

Error Handling

Common API Errors

For additional error handling guidance, see the LinkedIn API Error Handling Guide.

Best Practices

For All Tiers

✅ Always use LinkedIn-Version header for API compatibility
✅ Handle all verification states (fully verified, partially verified, not verified, not eligible)
✅ Use verificationUrl only for redirection – Don't expose or store it
✅ URL-encode your redirectUri before appending
✅ Validate id field uniqueness in your system
✅ Combine with /identityMe for complete member context
✅ Cache responses temporarily to reduce API calls

For Development Tier

⚠️ Remember: Only admin accounts can be accessed
💡 Test verification flows thoroughly before requesting Lite tier
💡 Verify badge display in your UI

For Plus Tier

✅ Use id field (not deprecated userId)
✅ Display verified names when showing identity verification
✅ Show organization info for workplace verifications
✅ Implement data freshness checks using lastVerifiedAt timestamps
✅ Use /validationStatus API for bulk freshness validation

Use Cases

All Tiers

• Display "Verified on LinkedIn" badges
• Confirm member trust and authenticity
• Trigger verification flows for unverified members
• Build trust scores based on verification status

Plus Tier Additional Use Cases

• Display verified legal name for identity confirmation
• Show verified company affiliation with logo
• Build detailed audit trails with verification timestamps
• Implement data freshness validation workflows
• Display verification methods for transparency

Related Resources

APIs

• Profile Details API – Get member profile information
• Validation Status API – Bulk validation checks (Plus tier only)

Guides

• Quickstart Guide – Get started with the API
• Upgrade to Lite Tier – Move to production
• Implementation Guide – Best practices
• Data Freshness Strategies – Keep data current (Plus tier)
• Certification Requirements – Production readiness (Plus tier)

Authentication

• Authorization Code Flow – OAuth 2.0 3-legged authentication

Other Resources

• Branding & UX Guidelines – Display verification badges correctly
• FAQ – Troubleshooting and answers
• Release Notes – API updates and current versions
• Overview – Product overview and tier comparison