List postsList fake blog posts, all 100 of them or just one user's, a page at a time. The stand-in content for a feed, a digest or a batch loop while the real source is still being built. No API key required.
Get a postGet one post by its id, with its title, body and author. The single-record fetch to point a step at while the real API is not ready yet. No API key required.
List commentsList fake comments, all 500 of them or just the ones on one post, a page at a time. Each carries a name, an email address and a body, which makes it stand-in data for a moderation queue or a notification digest. No API key required.
Get a commentGet one comment by its id, with the commenter's name, email address and text. No API key required.
List albumsList fake photo albums, all 100 of them or just one user's. Each album holds 50 photos, so an album id from here is what List photos wants. No API key required.
Get an albumGet one album by its id, with its title and the user it belongs to. No API key required.
List photosList fake photos, by album or across all 5,000. Every record carries a placeholder image URL and a thumbnail, so this is the step that fills a gallery mockup with pictures. Naming an album keeps it to that album's 50. No API key required.
Get a photoGet one photo by its id, with its full-size and thumbnail image URLs. No API key required.
List to-dosList fake to-dos, all 200 of them or just one user's, and keep only the ones that are done or only the ones that are not. Stand-in tasks for a reminder digest or a progress report while the real task system is still being wired up. No API key required.
Get a to-doGet one to-do by its id, with whether it is done. This is the record behind the service's own one-line example, and the quickest thing to point a first step at. No API key required.
List usersList the ten fake users, each a complete profile: name, handle, email, phone, site, postal address with coordinates, and an employer. The contact records to test a CRM sync, a mail merge or an address parser against. No API key required.
Get a userGet one user by their id: the whole fake profile, including the address, its coordinates and the company. No API key required.
Create a post (simulated)Send a post to JSONPlaceholder and get back what a real create would answer, without anything being stored. The way to prove a workflow assembles and sends the right body before you point it at a system that keeps what it is given. The answer carries the next id after the dataset's 100 posts, and fetching that id afterwards finds nothing. No API key required.
Update a post (simulated)Send a change to a post and get back what a real update would answer, without anything being stored. Change only the fields you set and the answer is the stored post with your changes applied; replace the whole post and the answer is exactly what you sent, so a field you leave out is gone from it. The difference is the point: it is how a workflow's update step gets tested both ways. No API key required.
Delete a post (simulated)Send a delete for a post and get back what a real delete would answer, without anything being removed. The post is still there afterwards, which is what makes this safe to run on a schedule while a workflow's delete step is being built. No API key required.
Check service statusCheck whether JSONPlaceholder is answering, and how quickly. This is the one action that reports a problem as a value instead of failing the step, so a workflow can branch on it, which is most of why anyone points a health check at this service. Being throttled is reported separately from being down. No API key required.
