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

JSONPlaceholder Posts API

100 sample blog posts owned by users

JSONPlaceholder Posts API is one of 7 APIs that JSONPlaceholder publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 12 JSON Schema definitions.

Tagged areas include Posts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a JSON-LD context, and 12 JSON Schemas.

This API exposes 11 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://jsonplaceholder.typicode.com, https://jsonplaceholder.typicode.com/.

11 operations 5 paths 4 schemas 2 DELETE5 GET2 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://jsonplaceholder.typicode.com
Resource Areas
1

Paths & Operations 11

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

Posts 11

100 sample blog posts owned by users

GET
/posts
JSONPlaceholder List Posts
listPosts 2 params → 200
POST
/posts
JSONPlaceholder Create Post
createPost body → 201
GET
/posts/{id}
JSONPlaceholder Get Post
getPost 1 param → 200404
PUT
/posts/{id}
JSONPlaceholder Replace Post
replacePost 1 param body → 200
PATCH
/posts/{id}
JSONPlaceholder Update Post
updatePost 1 param body → 200
DELETE
/posts/{id}
JSONPlaceholder Delete Post
deletePost 1 param → 200
GET
/posts/{id}/comments
JSONPlaceholder List Post Comments
listPostComments 1 param → 200
GET
/users/{id}/posts
JSONPlaceholder List User Posts
listUserPosts 1 param → 200
GET
/posts/{post-id}
Get post by ID
1 param → 200
PATCH
/posts/{post-id}
Update post
1 param body → 200
DELETE
/posts/{post-id}
Delete post
1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Comment (5 properties), post (4 properties), Post (4 properties), PostInput (3 properties). Each schema is shown below with its type and property counts.

PostInput
object
Payload for creating or partially updating a post.
3 properties
Post
object
A sample blog post owned by a user.
4 properties 4 required
Comment
object
A sample comment attached to a post.
5 properties 5 required
post
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jsonplaceholder-posts-api-openapi.yml Raw ↑

Other APIs JSONPlaceholder publishes across the network.

JSONPlaceholder Albums API
JSONPlaceholder Comments API
JSONPlaceholder Photos API
JSONPlaceholder Todos API
JSONPlaceholder Users API
JSONPlaceholder
Where this information came from

This is an independent, third-party profile of JSONPlaceholder Posts 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.