How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
LinkedIn

LinkedIn Use Cases > InMail Content API

You can set up the message contents sent to targeted LinkedIn members' inbox, either as a Message Ad or a Conversation Ad.

Documentation Provider Profile APIs.io OpenAPI GitHub

LinkedIn Use Cases > InMail Content API is one of 65 APIs that LinkedIn publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Use Cases > InMail Content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a changelog, release notes, and an API reference.

This API exposes 5 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.linkedin.com.

5 operations 3 paths 2 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.linkedin.com
Authentication
OAuth 2.0
Contact
LinkedIn API Support
Resource Areas
1

Authentication & Security 1

LinkedIn Use Cases > InMail Content API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2Auth) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Use Cases > InMail Content 5

You can set up the message contents sent to targeted LinkedIn members' inbox, either as a Message Ad or a Conversation Ad.

POST
/rest/inMailContents/
LinkedIn Create InMail Content
postCreateInmailContent 3 params body → 200
GET
/rest/inMailContents/{adInMailContentId}
LinkedIn Get InMail Content
getGetInmailContent 4 params → 200
POST
/rest/inMailContents/{adInMailContentId}
LinkedIn Update InMail Content
postUpdateInmailContent 4 params body → 200
GET
/rest/inMailContents
LinkedIn Batch Get InMail Content
getBatchGetInmailContent 5 params → 200
POST
/rest/inMailContents
LinkedIn Send Test InMail
postSendTestInmail 4 params body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

UpdateInmailContentRequest
string
CreateInmailContentRequest
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

linkedin-use-cases-inmail-content-api-openapi.yml Raw ↑

Other APIs LinkedIn publishes across the network.

LinkedIn Consumer API
AE Profile APIs.io
LinkedIn Access Control API
AE Profile APIs.io
LinkedIn Account Management API
AE Profile APIs.io
LinkedIn Ad Accounts API
AE Profile APIs.io
LinkedIn Ad Targeting Entities API
AE Profile APIs.io
LinkedIn Advertiser Transparency API
AE Profile APIs.io
LinkedIn Application Retrieval API
AE Profile APIs.io
LinkedIn Application Synchronization API
AE Profile APIs.io
LinkedIn Application Updates API
AE Profile APIs.io
LinkedIn Apply Connect Jobs API
AE Profile APIs.io
LinkedIn Audience Counts API
AE Profile APIs.io
LinkedIn Audience Insights API
AE Profile APIs.io
#Use Cases > InMail Content
← Back to L APIs
API Details
ID
linkedin:linkedin-use-cases-inmail-content-api
Base URL
https://api.linkedin.com
Docs
https://learn.microsoft.com/en-us/linkedin/consumer/
Provider
LinkedIn
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=linkedin-use-cases-inmail-content-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/linkedin-use-cases-inmail-content-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of LinkedIn Use Cases > InMail Content API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.