Status polling - Tera Contracted Supplier API

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.

Suggested poll cadence

Respect rate limits. A typical client polls every 15–60 seconds while status is received, then stops or slows down after a terminal commercial status.