https://github.com/ebx/ebx-linkedin-sdk
A pure Java LinkedIn API client which implements the v2 API.
https://github.com/ebx/ebx-linkedin-sdk
ebx-linkedin-sdk java linkedin linkedin-api linkedin-sdk
Last synced: 22 days ago
JSON representation
A pure Java LinkedIn API client which implements the v2 API.
- Host: GitHub
- URL: https://github.com/ebx/ebx-linkedin-sdk
- Owner: ebx
- License: apache-2.0
- Created: 2018-10-15T16:58:18.000Z (over 7 years ago)
- Default Branch: dev
- Last Pushed: 2025-11-13T10:24:54.000Z (3 months ago)
- Last Synced: 2025-11-13T12:14:45.619Z (3 months ago)
- Topics: ebx-linkedin-sdk, java, linkedin, linkedin-api, linkedin-sdk
- Language: Java
- Homepage:
- Size: 783 KB
- Stars: 46
- Watchers: 19
- Forks: 22
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Notice: NOTICE.txt
Awesome Lists containing this project
README
[](https://search.maven.org/search?q=g:%22com.echobox%22%20AND%20a:%22ebx-linkedin-sdk%22) [](https://raw.githubusercontent.com/ebx/ebx-linkedin-sdk/master/LICENSE)
# ebx-linkedin-sdk
## What it is
ebx-linkedin-sdk is a pure Java LinkedIn API client. It implements the versioning API as described
[here](https://docs.microsoft.com/en-us/linkedin/).
It is created and maintained by [Echobox](http://echobox.com).
## Licensing
ebx-linkedin-sdk itself is open source software released under the terms of the Apache 2.0 License.
## Installation (Recommended)
Recommended installation is via maven (or gradle etc.). For our latest stable release (recommended)
use:
```
com.echobox
ebx-linkedin-sdk
8.1.1
```
## Installation (Most Up To Date)
[](https://app.circleci.com/pipelines/github/ebx/ebx-linkedin-sdk)
If you'd like to use the latest SNAPSHOT build please ensure you have snapshots enabled in your pom:
```
oss.sonatype.org-snapshot
http://oss.sonatype.org/content/repositories/snapshots
false
true
```
and then include the snapshot dependency, replacing *x.x.x* with the latest
[snapshot version](https://github.com/ebx/ebx-linkedin-sdk/blob/dev/pom.xml):
```
com.echobox
ebx-linkedin-sdk
x.x.x-SNAPSHOT
```
alternatively just drop the JAR into your app and you're ready to go.
## Building it Yourself
Just type
mvn package
and the jars will be built and can be found in the `target` folder.
## Usage and examples
Please see the tests for examples of API calls that are supported and the expected JSON responses
To get the access token to begin to make requests ([See
documentation](https://docs.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow?context=linkedin/marketing/context])):
LinkedInClient client = new DefaultLinkedInClient(Version.DEFAULT_VERSION);
LinkedInClient.AccessToken accessToken = client.obtainUserAccessToken(clientId, clientSecret, redirectURI, code);
To create a LinkedIn Share
([See documentation](https://learn.microsoft.com/en-us/linkedin/marketing/integrations/community-management/shares/posts-api?tabs=http&view=li-lms-2023-01#create-a-post)):
VersionedPostConnection postConnection =
new VersionedPostConnection(new DefaultLinkedInClient(authToken));
Distribution distribution = new Distribution(Distribution.FeedDistribution.MAIN_FEED);
String commentary = "Message here"
Post post = new Post(ownerURN, commentary, distribution, Post.LifecycleState.PUBLISHED,
Post.Visibility.PUBLIC);
String articleLink = "https://www.example.com/1234";
String title = "title";
String description = "description";
PostUtils.fillArticleContent(post, articleLink, imageURN, title, description);
URN postURN = postConnection.createPost(post);
Retrieve an organization from LinkedIn
([See documentation](https://learn.microsoft.com/en-us/linkedin/marketing/integrations/community-management/organizations/organization-lookup-api?view=li-lms-2023-01&tabs=http#retrieve-an-administered-organization)):
VersionedOrganizationConnection connection =
new VersionedOrganizationConnection(linkedInClient);
Organization organization = connection.retrieveOrganization(organizationURN, null);
## Getting in touch
* **[GitHub Issues](https://github.com/ebx/ebx-linkedin-sdk/issues/new)**: If you have ideas, bugs,
or problems with our library, just open a new issue.
## Contributing
If you would like to get involved please follow the instructions
[here](https://github.com/ebx/ebx-linkedin-sdk/tree/master/CONTRIBUTING.md)
## Releases
We use [semantic versioning](https://semver.org/).
All merges into DEV will automatically get released as a maven central snapshot, which can be easily
included in any downstream dependencies that always desire the latest changes (see above for
'Most Up To Date' installation).
Each merge into the MASTER branch will automatically get released to Maven central and github
releases, using the current library version. As such, following every merge to master, the version
number of the dev branch should be incremented and will represent 'Work In Progress' towards the
next release.
Please use a merge (not rebase) commit when merging dev into master to perform the release.
To create a full release to Maven central please follow these steps:
1. Ensure the `CHANGELOG.md` is up-to-date with all the changes in the release, if not please raise
a suitable PR into `DEV`. Typically, the change log should be updated as we go.
2. Create a PR from `DEV` into `MASTER`. Ensure the version in the `pom.xml` is the
correct version to be released. Merging this PR into `MASTER` will automatically create the maven
and github releases, **This PR should never be squashed, but just merged** to ensure all commits
from dev are included in master. Please note that a release is final, it cannot be undone/deleted/overwritten.
3. Once the public release has been successful, create a final PR into `DEV` that contains an
incremented `pom.xml` version to ensure the correct snapshot gets updated on subsequent merges
into `DEV`. This PR should include:
* An update to the `README.md` latest stable release version number.
* A 'Work In Progress' entry for the next anticipated release in `CHANGELOG.md`.