LinkedIn profiles, company pages, posts, comments and job listings, plus people search, messages, invitations and connections through a LinkedIn account you connect.
- Unified
Account,Post,Comment,Publication- Soon
- Direct
- 31 endpoints from 2 vendor APIs
- Live
Unified
Ask for Account, Post and Comment
SoonYou name the data; AIsa answers from Unipile or TikHub, whichever is fresh and working, and can switch between them without touching your code. Every value is tagged with its source, and you pay only when something comes back.
Planned calls
A first draft. None of these is callable yet, and names and fields may change.
| Call | Returns | Sources behind it | From | Direct paths |
|---|---|---|---|---|
| Account2 calls | ||||
| Look up an account | Account | Unipile, TikHub | Soon | — |
| Followers of an account | Account[] | Unipile, TikHub | Soon | — |
| Post2 calls | ||||
| Recent posts from an account | Post[] | Unipile, TikHub | Soon | — |
| Search posts | Post[] | Unipile, TikHub | Soon | — |
| Comment1 call | ||||
| Comments under a post | Comment[] | Unipile, TikHub | Soon | — |
| Write1 call | ||||
| Publish a post | Publication | Your connected account | Soon | — |
Direct
Or call a vendor's endpoint yourself
LiveThe same LinkedIn data through each vendor's own paths and fields, on your AIsa key. You pick the vendor, and your code is written against its format, so switching later means rewriting the call.
Unipilefrom $0.000001
unipile23 endpoints23 of its 24 endpoints cover LinkedInGET /apis/v1/unipile/linkedin/search/parametersReturns Unipile’s own JSONTikHubfrom $0.001tikhub8 endpoints8 of its 954 endpoints cover LinkedInGET /apis/v1/tikhub/linkedin/web_v2/get_company_postsReturns TikHub’s own JSONEvery LinkedIn endpoint
Read live from api.aisa.one. Metered prices start at the amount shown and vary with the request. A path opens its page in the docs.
| Method | Path | Name | Price |
|---|---|---|---|
| Unipile23 endpoints | |||
| GET | unipile/linkedin/company/{identifier} | Company Profile | $0.01 |
| GET | unipile/linkedin/me | Own Profile | $0.005 |
| GET | unipile/linkedin/recruiter/job-slots-credits/{account_id} | Recruiter Job Slots Credits | $0.005 |
| POST | unipile/linkedin/search | LinkedIn People Search | $0.02 |
| GET | unipile/linkedin/search/parameters | LinkedIn Search Parameters | $0.000001 |
| GET | unipile/linkedin/users/{identifier} | User Profile | $0.01 |
| GET | unipile/linkedin/chats | Chat List | $0.005 |
| POST | unipile/linkedin/chats/send | Start Chat | $0.02 |
| TikHub8 endpoints | |||
| GET | tikhub/linkedin/web_v2/get_company_posts | linkedin get_company_posts | from $0.05 |
| GET | tikhub/linkedin/web_v2/get_company_profile | linkedin get_company_profile | from $0.008 |
| GET | tikhub/linkedin/web_v2/get_job_detail | linkedin get_job_detail | from $0.05 |
| GET | tikhub/linkedin/web_v2/get_post_comments | linkedin get_post_comments | from $0.05 |
| GET | tikhub/linkedin/web_v2/get_post_detail | linkedin get_post_detail | from $0.001 |
| GET | tikhub/linkedin/web_v2/get_user_posts | linkedin get_user_posts | from $0.05 |
| GET | tikhub/linkedin/web_v2/get_user_profile | linkedin get_user_profile | from $0.008 |
| GET | tikhub/linkedin/web_v2/search_jobs | linkedin search_jobs | from $0.05 |
Which one to use
Unified
When you want fields that stay the same across vendors and platforms, a fallback when one source fails, and to pay only when something comes back.
Direct
When you need a parameter or field only one vendor has, or you've already built on that vendor's format.
The same Account and Post everywhere
An account on LinkedIn comes back with the same fields as one on X, so a prompt written for one platform works on the next.
