> ## Documentation Index > Fetch the complete documentation index at: https://docs.usejuiced.com/llms.txt > Use this file to discover all available pages before exploring further. # Logs > Incoming and outgoing logs, plus the ping and post inspectors, which are the receipts for every request in and out of Juiced. Every request that touches Juiced leaves a receipt. When a source pings or posts, Juiced records an **incoming log**. When Juiced pings or posts to a partner, or sends a lead to a customer's webhook, it records an **outgoing log**. Together they answer the two questions you'll ask most, "What did they send us?" and "What did we send them?" Both live under **Entries** in the sidebar, next to **Leads**. ## Incoming logs An incoming log (also called a distribution flow) is one run of the pipeline, covering a ping, a post, the lead it created, and every [distribution stage](https://docs.usejuiced.com/features/distribution.md) the lead visited. Open **Incoming logs** to see them all, newest first. ![Incoming logs list with Source, Ping, Post, Lead, Honored, Recipient, and Sold For columns, a search box, and a Filters button](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/incoming-logs-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=87f00f14948c388a054e1bb58f78f09c) | Column | What it shows | | - | - | | **Source** | The source that sent the traffic and when. A Test badge marks test traffic, and an Error badge marks a flow that hit a distribution error. | | **Ping** | The ping's outcome, Matched, No Match, Pending, or Rejected. Blank means there was no ping (a direct post). | | **Post** | What happened when the full lead was posted. | | **Lead** | The lead that was created, linked to its page. A Deleted badge means the lead was later deleted. | | **Honored** | Honored when a ping's accepted offer won the lead on the post. | | **Recipient** | The customer or partner who received the lead. | | **Sold For** | What the lead sold for. | The search box matches source and recipient names. Click **Filters** to narrow the list by any of these. * **Ping** status and **Source** * **Has Ping**, **Ping Honored**, **Has Post**, **Has Lead**, and **Assigned** (each Yes or No) * **Recipient Type** (Customer or Partner) and **Channel Type** (Bid, Customer, or Ping/Post) * **Test mode** (real traffic by default, or test only) * **Created** date range Filters are kept in the page URL, so you can bookmark or share a filtered view. ### Inside an incoming log Click a row to open it. The page title is the log's ID (it starts with `dflow_`). ![Incoming log with an Inbound, Routing, and Outbound timeline, Details and Records in the sidebar, and an empty Outgoing logs table](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/incoming-log-detail-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=dff96aa860da790625a6053895e194b5) * **Timeline** has three lanes. **Inbound** holds what the source sent (the ping and post), **Routing** holds what Juiced did with it (lead created, each stage's result, who won), and **Outbound** holds pings and posts Juiced sent to partners. Each card describes its event in plain language and links to the related ping, post, or lead where there is one. * **Details** shows the flow's **Status**, **Mode** (Live or Test), **Duration**, and when it was **Initiated**. * **Records** links to the **Source**, **Lead**, **Recipient**, **Ping**, and **Post**, plus **Offers** (the number of offers made, with a **View** link). * **Outgoing logs** lists every partner ping and post this flow triggered, with date, type, partner, result, and price. ### Offers Click **View** next to **Offers** to see every offer the lead attracted. The dialog lists each bidder's **Name** (the winner is badged Winner), **Channel**, **Bid**, **Effective** price, **Penalty** (hover it for the reason), **Score**, **Discount**, **Charged**, and **Status**. It's the fastest way to see why one buyer beat another. See [ping-post](https://docs.usejuiced.com/features/ping-post.md) for how offers are scored. ## Outgoing logs **Outgoing logs** lists every request Juiced sent out, including pings and posts to [partners](https://docs.usejuiced.com/features/partners.md) and webhook deliveries. Rows are grouped by the incoming log they belong to, with a **View log** link to jump back to it. ![Outgoing logs list grouped by log number, with date, type, partner, result, price, and a View log link on each row](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/outgoing-logs-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=ca710b6cc045a700c07d6ce30f303f3c) The search box matches partner names and endpoint URLs. **Filters** cover these options. * **Type** (Ping, Post, or Webhook) * **Result** (Pending, Succeeded, Duplicate, Rejected, HTTP error, Timeout, Validation failed, or Error) * **Partner** * **Test mode** (real traffic by default, or test only) * **Created** date range Click a row to see the full exchange. ![Successful outgoing post with the request payload, the partner's response, and Details in the sidebar](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/outgoing-log-detail-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=d1c53ef67f0519eb0c9b1ecad3c07277) * **Request** shows what Juiced sent, as **Payload**, **Headers**, or **Raw body**. * **Response** shows what the partner sent back, as **Body**, **Headers**, or **Raw body**. When something went wrong on our side of the wire, an **Error** tab shows the error class and message. * **Details** lists **Result**, **Type**, **Mode**, **Partner**, **Price**, **Response code**, **Method**, **Format** (JSON or Form), **Duration**, **Timestamp**, and **Endpoint**. * **Records** links to the incoming log. ![Outgoing post with an HTTP error result, a 503 response code, and a response body reading Service temporarily unavailable](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/outgoing-log-detail-failed-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=cdf1862325fb8f1db2a66fb704b8e710) A failed post, where the partner's endpoint answered with a 503. ## Ping and post inspectors Pings and posts don't have their own list pages. You reach them from an incoming log (the **Ping** and **Post** links under **Records**, or **View ping** / **View post** on a timeline card), or from a lead's **View Ping** and **View Post** actions. ### Ping inspector Shows exactly what a source sent to the [ping endpoint](https://docs.usejuiced.com/api-reference/endpoint/ping.md) and what Juiced answered. ![Ping inspector with the request payload, a response body containing a price and Match found message, and Details and Records in the sidebar](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/ping-inspector-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=c6189e99e16629bce6f280738d488dd0) * **Request** shows the **Payload** and **Headers**, plus **Validation errors** when the ping was rejected. * **Response** shows the **Body** and **Headers** Juiced returned, including the price offered. * **Details** lists the response **Status** code, **Mode**, **Source**, **Method**, **Timestamp**, and ping **ID**. * **Records** shows the **Source**, **Lead category**, **Lead type**, **County**, and **Postal code** the ping resolved to. ### Post inspector A post (also called a [submission](https://docs.usejuiced.com/features/submissions.md)) is the full lead a source sent to the [leads endpoint](https://docs.usejuiced.com/api-reference/endpoint/leads.md). Every post is stored as received, whether or not it became a lead. ![Post inspector with the request payload, Juiced's response, and Details and Records in the sidebar](https://mintcdn.com/juicedleads/M7vM08I9VkWrtgG1/images/tenant/logs/post-inspector-light.webp?fit=max\&auto=format\&n=M7vM08I9VkWrtgG1\&q=85\&s=d3ed56f413730d5815a6e6d190673bb3) * **Request** shows the **Payload** as received (even fields that don't map to anything in your lead category), plus **Validation errors** when the post was rejected. * **Response** shows the **Body**, **Headers**, and **Raw body** Juiced sent back. * **Details** lists **Status** (Pending, Accepted, or Rejected), **Mode**, **Source**, **Response code**, **Duration**, **Timestamp**, and **ID**. * **Records** links to the **Lead** the post created, if any. | Post status | Meaning | | - | - | | Pending | Still being processed. This is a brief, transient state. | | Accepted | Passed validation and produced a lead. | | Rejected | Failed validation; no lead was created. Check **Validation errors** for the field-by-field reasons. | > [!TIP] > > Test traffic is hidden by default. When a vendor is testing their integration, set the **Test mode** filter to **Test only** on Incoming logs to find their requests. ## Permissions Each log screen has its own permission, so you can give a support teammate access to the logs without access to everything else. Incoming logs, outgoing logs, pings, posts, and offers are each controlled separately in [roles](https://docs.usejuiced.com/features/roles.md). ## Related pages * [Reading distribution logs](https://docs.usejuiced.com/guides/reading-distribution-logs.md) * [Distribution](https://docs.usejuiced.com/features/distribution.md) * [Ping-post](https://docs.usejuiced.com/features/ping-post.md) * [Sending leads to Juiced](https://docs.usejuiced.com/guides/sending-leads-to-juiced.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.