Delivery contract

POST /v2/supplier-submissions accepts the same basic body as v1, with one extra rule: email is required and must be an address the CRM can store. A missing email, or a reserved suffix such as .test, is a validation error. Nothing is stored. Commercial acceptance still happens on the existing worker. Acceptance is not permission to purchase or charge the supplier. After acceptance, Tera creates or reuses one Application and enqueues pre-underwriting. The same external_reference and body replay the existing submission. A replay does not change a v1 row into a v2 row. /v1 is unchanged. Basic submissions created there still wait for promotion. Promotion remains available. Historical unpromoted submissions are not promoted by this contract. Billing follows the agreement already snapshotted on the submission. This route does not change which submissions are billable. Document-first agreements receive arrival_screen_url on an enrolled delivery submission, the same way an application-level submission does. Company number and business structure stay optional on a basic body. When they are absent, Tera mints the Application locally and waits to project a HubSpot deal until that identity exists. It does not invent a company structure.

What this route does not do

It does not return BUY, REVIEW, or NO BID.
It does not turn Application creation into a purchase or a charge.
It does not enable the legacy lead-acquisition auction.
It does not send a second customer email when the existing document-first arrival notify already ran.

Suppliers whose current contract requires an auction response before the full lead is delivered keep that auction. Moving them onto this delivery route is an external contract change. Do not send live auction traffic to /v2 until that change is agreed.

Example

Same synthetic applicant as the basic guide, including email.

{
  "external_reference": "northbridge-enq-2002",
  "level": "basic",
  "first_name": "Amelia",
  "last_name": "Hart",
  "telephone": "07700 900123",
  "email": "amelia.hart@example.com",
  "business_name": "Northbridge Tea Rooms Ltd",
  "funding_amount": 25000,
  "funding_purpose": "working-capital",
  "contact_expectation": {
    "permission_stated": true,
    "channels": ["phone"],
    "wording_version": "supplier-v1-pending",
    "captured_at": "2026-08-29T09:00:00.000Z"
  },
  "capture_timestamp": "2026-08-29T09:00:00.000Z",
  "attribution": { "source": "sandbox-guide" }
}

POST /v2/supplier-submissions returns 202 received for a new body and 200 for an identical replay. received is still not billable. The Application reference appears on a later poll, after the commercial decision, the same way an application-level submission does.

Get started

Submit enquiries

After you submit

Errors and limits

What this route does not do

Example

​What this route does not do

​Example

What this route does not do

Example