Status polling

Poll until status leaves received, or until you have the identifiers you need for reconciliation. Requires supplier_submissions:read.

Endpoints

GET /v1/supplier-submissions/{submission_id}
GET /v1/supplier-submissions?external_reference=northbridge-enq-1001

Both are tenant-scoped. An unknown id and a cross-tenant id return the same 404.

Supplier-visible object

{
  "environment": "sandbox",
  "submission_id": "11111111-1111-4111-8111-111111111111",
  "external_reference": "northbridge-enq-1001",
  "level": "basic",
  "status": "received",
  "received_at": "2026-08-29T09:00:00.000Z",
  "decided_at": null,
  "application_reference": null,
  "application_created_at": null,
  "billing": {
    "billing_status": "not_billable",
    "billable_at": null,
    "billing_model": "accepted_submission",
    "not_billable_reason": "sandbox"
  }
}

Commercial statuses

`status`	Meaning
`received`	Technical acknowledgement. Not accepted. Not billable.
`accepted`	Commercially accepted. Application fields appear only when an Application exists.
`duplicate_not_accepted`	Not accepted because Tera already has an active funding journey. No Case Reference of the match is returned.
`rejected`	Not accepted under the applicable rules.

Billing is a separate object (pending / billable / not_billable). Tera does not return processing retries, broker assignment, grades, or match identity. handoff is omitted until a usable unused Journey Entry Link exists. Never handoff: null. Unenrolled, basic, rejected, and duplicate_not_accepted responses never include it.

Enrolled Supplier Handoff

When the active agreement has document_first_journey: true, an accepted application-level submission (or a later Promotion that minted an Application) may include:

{
  "handoff": {
    "customer_journey_url": "https://client.terabusinessfinance.com/apply/continue?token=…&dealId=…&next=documents",
    "expires_at": "2026-08-30T09:12:00.000Z",
    "single_use": true
  }
}

customer_journey_url is a Journey Entry Link. It does not contain HubSpot ids, email, phone, name, or amount.

POST /v1/supplier-submissions still returns 202 received (identical fingerprint replay may be 200).
Poll about every 500ms with light backoff.
Enrolled create already redirected via arrival_screen_url. Poll is for your records. When status === "accepted" and handoff.customer_journey_url is present, you may store that Journey Entry Link — do not wait for it to move the Applicant.
rejected or duplicate_not_accepted still have no handoff. The Applicant who already hopped is on the Arrival Screen.
Unenrolled clients: if still received after 30–60 seconds, show your own error and stop polling.

const created = await postSubmission(body);
// Enrolled: 202 { status: "received", arrival_screen_url }
if (created.arrival_screen_url) {
  window.location = created.arrival_screen_url;
}

Suggested poll cadence

Respect rate limits. Unenrolled clients typically poll every 15–60 seconds while status is received. Enrolled document-first clients redirect from create; poll only if you need commercial/billing records.

Get started

Submit enquiries

After you submit

Errors and limits

Endpoints

Supplier-visible object

Commercial statuses

Enrolled Supplier Handoff

Suggested poll cadence

​Endpoints

​Supplier-visible object

​Commercial statuses

​Enrolled Supplier Handoff

​Suggested poll cadence

Endpoints

Supplier-visible object

Commercial statuses

Enrolled Supplier Handoff

Suggested poll cadence