Skip to main content
A submission (shown in the panel as a post) is the exact payload a source sent to the leads endpoint, captured before any processing happens. Juiced keeps it whether or not it became a lead, so you have a reliable record of what was sent, separate from the lead that may or may not have been created from it. Pings sent to the ping endpoint are recorded separately as pings.

​
Why submissions exist

Leads are the cleaned, validated, categorized result of a post. Submissions are the original data. They’re useful in cases like these.
  • A source is reporting that a lead wasn’t created, and you need to see what they actually sent.
  • Validation is rejecting leads and you need the original payload plus the exact validation errors.
  • You’re building an integration and want to inspect what Juiced received versus what you thought you sent.
Every lead that came in through the API has one submission behind it. Rejected submissions never become leads.

​
What a submission stores

  • Source is the source that posted the data.
  • Payload is the request body as received, preserved as-is, even for fields that don’t map to anything on your lead category.
  • Status is Pending (briefly, while processing), Accepted (became a lead), or Rejected (failed validation).
  • Validation errors holds the field-by-field errors returned to the caller for rejected posts.
  • Response is what Juiced sent back, with the response code and how long it took.
  • Mode is Live, or Test when the post came through a test-mode source.

​
Where to find submissions

There’s no separate list of posts. You open one from either of two places.
  • In an incoming log, click the Post link under Records, or View post on the timeline.
  • In a lead’s More actions menu, choose View Post.
Both open the post inspector, which shows the request, response, and status side by side.
“Post” here means the HTTP POST a source made to create the submission. In ping-post, the post is the follow-up request that delivers the full lead after a successful ping, so in a ping-post flow they’re the same thing.