DummyJSON

• List productsList DummyJSON's 194 fake products, each with a price and a discount, stock, brand, category, rating, reviews, pictures, SKU and barcode. Search their titles and descriptions, keep one category, sort by price, rating, stock or last change, and page through. The stand-in catalogue for a store workflow while the real one is being built. No API key required.
• Get a productGet one product by its id, with everything DummyJSON holds on it: the price before and after its discount, stock, reviews, pictures, size, SKU and barcode. No API key required.
• List product categoriesList DummyJSON's 24 product categories, each with its slug, its name and how many products are in it. The slug is what List products and Add a product take. No API key required.
• Add a product (simulated)Send a new product to DummyJSON and get back what a real create would answer, without anything being stored: the product as sent, under the next id after the catalogue's last. DummyJSON keeps ten fields of a product (title, description, price, discount, stock, rating, brand, category, thumbnail and pictures) and drops anything else. The way to prove a workflow puts the right product together before pointing it at a real store. No API key required.
• Update a product (simulated)Send a change to a product and get back what a real update would answer, without anything being stored: the product with the fields you set applied. DummyJSON answers with the ten fields a product write can change, so tags, reviews and the like come back empty. No API key required.
• Delete a product (simulated)Send a delete for a product and get back what a real delete would answer: the whole product and the moment it was deleted. Nothing is removed, so Get a product still finds it and this can run again on the same id. No API key required.
• List cartsList DummyJSON's 208 fake shopping carts, or one user's, each priced line by line with quantities, discounts and totals. Sort by total or by how much is in them, and page through. No API key required.
• Get a cartGet one cart by its id: each product in it with its quantity, price, discount and line total, and the cart's total before and after discounts. No API key required.
• Add a cart (simulated)Put a cart together for a user from product ids and quantities, and get it back priced by DummyJSON: each line multiplied out and discounted, and the cart totalled. Nothing is stored. Product ids DummyJSON does not have are left out of the cart and listed separately. A realistic order to test a checkout, invoice or receipt workflow with. No API key required.
• List usersList DummyJSON's 208 fake people, each a whole profile: name, age, email, phone, home address with coordinates, employer, university, bank card, and the username and password that log them in. Search by name, email or username, keep the people with a given role, city, department or the like, sort, and page through. No API key required.
• Get a userGet one of DummyJSON's fake people by their id: the whole profile, from home address and employer to the username and password Log in as a test user takes. No API key required.
• List postsList DummyJSON's 251 fake blog posts, with their tags, likes, dislikes and views. Search their text, keep one tag or one author's posts (these combine), sort by views or likes, and page through. No API key required.
• Get a postGet one blog post by its id, with its text, tags, likes, dislikes, views and its author's id. No API key required.
• List commentsList DummyJSON's 340 fake comments, or the ones on one post, each with its likes and the commenter's name and username. No API key required.
• List to-dosList DummyJSON's 254 fake to-dos, or one user's, and keep only the done or only the open ones. Stand-in tasks for a reminder or progress workflow. No API key required.
• Get random quotesGet one to ten random quotes from DummyJSON's 1,454, each with its author, different every time. The quote of the day for a newsletter, a chat post or a screen. No API key required.
• List recipesList DummyJSON's 50 fake recipes, each with ingredients, steps, times, servings, calories, cuisine and a rating. Search by name, keep a tag, a meal, a cuisine or a difficulty (they combine), sort by rating or time, and page through. No API key required.
• Get a recipeGet one recipe by its id: ingredients, step by step instructions, preparation and cooking time, servings, calories and a photo. No API key required.
• Log in as a test userLog in as one of DummyJSON's fake users and get a real, signed access token (a JWT) and a refresh token, with the user's short profile. Every user's username and password are in their record; user 1 is emilys, password emilyspass. For testing a login flow or a step that needs a bearer token. No API key required.
• Get the logged-in userGet the user an access token from Log in as a test user belongs to: the whole profile. It proves the token works, and says why when it does not. No API key required.
• Refresh a login sessionTrade a refresh token for a new access token and a new refresh token, the way an app keeps someone logged in. No API key required.
• Create a test webhookMake a temporary address that records every request sent to it for 24 hours. Point another service or a workflow's HTTP step at it, then read what arrived with List a test webhook's requests; opening the address in a browser shows DummyJSON's live inspector. DummyJSON allows 10 new test webhooks an hour. No API key required.
• Send a request to a test webhookSend a request into a test webhook, the way another system would call it: any method, a JSON body and query parameters. For rehearsing a callback, or checking what the webhook records. No API key required.
• List a test webhook's requestsList what a test webhook has received, newest first: each request's method, headers, query parameters, body and time. It can wait up to two minutes for something to arrive, and keep only what came in after a given moment. DummyJSON keeps a webhook's latest 100 requests, and keeps JSON and form bodies only. No API key required.
• Create a mock endpointGet a public address that answers with the JSON you give it: a stand-in for an API that does not exist yet. The same JSON and method always get the same address, and DummyJSON deletes one nobody has called for 90 days. Anyone with the address can call it, so keep secrets out of it. No API key required.
• Simulate an HTTP statusHave DummyJSON answer with the status code of your choosing, 404, 429 or 503 say, and a message of your own. The answer comes back as a value, or an error status can fail the step, for rehearsing what a workflow does when a service it calls fails. No API key required.
• Make a placeholder imageGet the address of a placeholder image of any size up to 4000 pixels a side, with your own caption, colors, font and format (PNG, JPEG or WebP). The image is made and checked before the address comes back. For mockups, emails and test posts. No API key required.
• Make an identiconGet the address of an identicon: a pattern drawn from any text, the same every time, for a default avatar. DummyJSON's users have these as their avatars, so a username's identicon matches that user's picture. No API key required.
• Generate a 2FA code for a test accountGet the current six-digit two-factor code for a test account: the code Google Authenticator or Authy would show for it, so a scripted sign-in can get past its 2FA step. You supply the account's own secret, the key its authenticator was set up with or the otpauth link in its QR code; this action does not make one up. That secret is sent to DummyJSON's servers to work the code out, and whoever holds it can make the account's codes for good, so use this only with a test account's secret, never a real account's. The example, JBSWY3DPEHPK3PXP, is the public test secret from DummyJSON's docs. No API key required.

No actions match that.