Share via


Parent-child application

Overview

Parent-child applications are associated with child products. A child product is defined as an API product that can be requested in one of two ways:

  1. By a standalone application, which then becomes a parent application
  2. through the "Child app" sub-tab on the 'Products' page of a parent application on developer.linkedin.com.

The provisioned child-API product would then be visible in the "Child app" sub-tab under the "Added products" section on the 'Product' page of the same parent application.

Parent Application

A LinkedIn developer application that has at least one approved child product added to it and which is designated as 'App type: Parent app' in the developer portal is termed as a parent application.

Typically, if the requested API product operates on a parent-child paradigm, the standalone developer application provided by the partner, if applicable, is transformed into a parent application during API product provisioning.

If the developer application is designated as a parent application for API product usage, the API products are assigned at the child-app level.

This necessitates that the partner create further child apps using the provisioning API to access the API endpoints.

Child Applications

Child applications are customer applications that are typically assigned to individual customers. To meet the specific API requirements of each customer, it is necessary to use the child application that has been dedicated to them.

To create child applications, you can use the provisioning API, which enables you to create a child developer application with its own client ID and secret. These child applications are created using an access token generated from the parent application's API key. APIs mentioned under the child-app section can be accessed via an access token generated using a child application's API key.

Error Codes

The following error codes can be returned:

ERROR CODE DESCRIPTION
403 Not enough permissions to access: In the case where the access token generated from the parent-app is used to make a call to the APIs defined under the child-app of the same parent-app, an HTTP 403: Forbidden response code is returned. To access the APIs defined under child-product, an access token should be generated using a child-application.