Share via

Member Authorization Management API

  • Article

Once the user has consented and the access token is generated, LinkedIn automatically start processing and archiving both Changelog and Snapshot data, it usually takes a few minute for the data to be present in the API responses. Please use Member Changelog API and Member Snapshot API to query the respective data. If after the access token is generated and data is still not available after a few minutes, the following APIs can be used to check if the member has been registered for DMA member data generation.

Note

Once a user consents and access token is generated, they are automatically registered for processing and archiving their LinkedIn data. The Member Authorization APIs are to be used only for debugging if you are not seeing LinkedIn data in the responses to the Member Changelog and Member Snapshot APIs after a few minutes of access token generation.

The following member FINDER API can be used to check if a member is registered for DMA and LinkedIn data for the member is being processed and archived.

GET https://api.linkedin.com/rest/memberAuthorizations?q=memberAndApplication

sample GET response

{
  "elements": [
    {
      "memberComplianceAuthorizationKey": {
        "developerApplication": "urn:li:developerApplication:123456",
        "member": "urn:li:person:123ABC",
      },
      "regulatedAt": 1698382869085,
      "memberComplianceScopes": [
                "DMA"
      ],
    }
  ]
}

memberComplianceAuthorization Response Schema

Field Name Description Data Type
regulatedAt Epoch timestamp since which the user's compliance activities are being monitored and archived long
memberComplianceAuthorizationKey.developerApplication developer application which the user has consented to URN String
memberComplianceAuthorizationKey.member user whose compliance events are being archived (This the user whose token is being used) URN String
memberComplianceScopes Array of Compliance Products, the user has consented to. This would contain only be "DMA" Array of ENUM

Once the user has consented and an access token is generated, LinkedIn starts processing and archiving both changelog and snapshot data for the user. It usually takes a couple of seconds to enable data generation for the user. You can also enable data generation for a user manually by calling the following API:

POST https://api.linkedin.com/rest/memberAuthorizations
Request Body {}

Note

You will need to supply an empty JSON object, {} to the request body to successfully enable changelog event generation for the user.