web-dev-qa-db-ja.com

LinkedInアカウントに関するすべての可能な情報を取得する方法(C#を使用したAPI)

LinkedinのAPI を使用するC#アプリを作成しています。

「個人」(名+姓)を照会し、このグループの人々に関するすべての可能な情報を取得できるようにしたいwith the same name

現在、 People-Search APIコールと一緒に REST API の独自の実装を使用しています。

動作することがわかっているリクエストの例を次に示します。

https://api.linkedin.com/v1/people-search:(people:(id,first-name,last-name,headline,picture-url),num-results)?

私はそれを実行しています:first-name=parameter&last-name=parameter after the ? mark

問題は、タイトル、業界、現在の会社、現在の学校などの詳細情報を取得したいことです。可能なパラメーターのリストについては、 here を参照してください。

この表記は、彼らが呼ぶものです フィールドセレクター

誰かに関するすべての可能な情報を取得できるように、APIコールをどのように構成しますか?

31

すでに表記法がわかっているので、残りのフィールドセレクターを追加し、必要に応じてネストします。

https://api.linkedin.com/v1/people-search:(people:(id,first-name,last-name,headline,picture-url,industry,positions:(id,title,summary,start-date,end-date,is-current,company:(id,name,type,size,industry,ticker)),educations:(id,school-name,field-of-study,start-date,end-date,degree,activities,notes)),num-results)?first-name=parameter&last-name=parameter

Profile Field docs ごとに、現在のユーザーの第1度の接続についてのみ教育を受けることができることに留意してください。

23
Paul Mennega

ユーザープロファイルのすべてを取得するURLは次のとおりです。

https://api.linkedin.com/v1/people/~:(id、first-name、last-name、headline、picture-url、industry、summary、specialties、positions:(id、title、概要、開始日、終了日、現在、会社:(ID、名前、タイプ、サイズ、業界、ティッカー))、教育:(ID、学校名、研究分野、開始日、終了日、学位、活動、メモ)、協会、関心、生年月日、生年月日、出版物:(id、title、publisher:(name)、authors:(id、name)、date、url、要約)、patents:(id、title、summary、number、status:(id、name)、office:(name)、inventors:(id、name)、date、url)、languages:(id、language:(name )、proficiency:(level、name))、skills:(id、skill:(name))、certifications:(id、name、authority:(name)、number、start-date、end-date)、courses :( id、name、number)、recommendations-received:(id、recommendation-type、recommendation-text、recommender)、honors-awards、three-current-positions、three-past-positions、volunteer)?oauth2_access_token = PUT_YOUR_TOKEN_HERE

Oauth2アクセストークンが必要です。

これは、ニース文字列リスト(Java)にあります。

apiUrl
    + "/v1/people/~:("
        + "id,"
        + "first-name,"
        + "last-name,"
        + "headline,"
        + "picture-url,"
        + "industry,"
        + "summary,"
        + "specialties,"
        + "positions:("
            + "id,"
            + "title,"
            + "summary,"
            + "start-date,"
            + "end-date,"
            + "is-current,"
            + "company:("
                + "id,"
                + "name,"
                + "type,"
                + "size,"
                + "industry,"
                + "ticker)"
        +"),"
        + "educations:("
            + "id,"
            + "school-name,"
            + "field-of-study,"
            + "start-date,"
            + "end-date,"
            + "degree,"
            + "activities,"
            + "notes),"
        + "associations," /* Full Profile */
        + "interests,"
        + "num-recommenders,"
        + "date-of-birth,"
        + "publications:("
            + "id,"
            + "title,"
            + "publisher:(name),"
            + "authors:(id,name),"
            + "date,"
            + "url,"
            + "summary),"
        + "patents:("
            + "id,"
            + "title,"
            + "summary,"
            + "number,"
            + "status:(id,name),"
            + "office:(name),"
            + "inventors:(id,name),"
            + "date,"
            + "url),"
        + "languages:("
            + "id,"
            + "language:(name),"
            + "proficiency:(level,name)),"
        + "skills:("
            + "id,"
            + "skill:(name)),"
        + "certifications:("
            + "id,"
            + "name,"
            + "authority:(name),"
            + "number,"
            + "start-date,"
            + "end-date),"
        + "courses:("
            + "id,"
            + "name,"
            + "number),"
        + "recommendations-received:("
            + "id,"
            + "recommendation-type,"
            + "recommendation-text,"
            + "recommender),"
        + "honors-awards,"
        + "three-current-positions,"
        + "three-past-positions,"
        + "volunteer"
    + ")" 
    + "?oauth2_access_token="+ token;
39
BDG
11