FreightBlast by Doft

API for partners

Put audience, eligibility and outcomes inside your product

A scoped API for selected partners: define an audience, ask whether a contact and channel may be used, record the conversation and receive the accepted result as a signed event.

Request partner accessSee the policy gates

  1. Your product

    Partner backend

    • Send audience definition
    • Read eligibility
    • Receive outcomes

  2. FreightBlast API

    Scoped to your tenant

    • Audience estimate
    • Eligibility decision
    • Conversation record
    • Outcome events

  3. Governed delivery

    Policy before sending

    • Suppression and consent
    • Sender and provider
    • Allow or block

Capabilities

Four capabilities, and what each is for

Audience

Define and estimate an audience inside your own product.

Available to approved partners

Eligibility

Ask whether a contact and channel may be used, before you send.

Available to approved partners

Conversation

Record an approved message and the reply it produced.

Available to approved partners

Outcomes

Receive accepted results as signed events.

Available to approved partners

Example

Estimate an audience

One validated call. Everything else in the API follows the same shape: scoped token, explicit tenant, idempotent write.

POST /v1/audiences/estimate
Authorization: Bearer <scoped access token>
Content-Type: application/json
Idempotency-Key: 8f1c0b34-1f7a-4b0e-9f2a-3d5b7c9e1a20

{
  "tenant": "acme-insurance",
  "definition": {
    "vertical": "insurance",
    "power_units": { "min": 10, "max": 75 },
    "states": ["TX", "OK", "NM"],
    "signals": ["authority_reinstated", "insurance_filing_lapsed"]
  }
}

Request

200 OK
Content-Type: application/json

{
  "estimate": { "matched": 1284, "sourced": 1147, "unknown": 137 },
  "signals": {
    "authority_reinstated": { "last_30_days": 61, "source": "FMCSA" },
    "insurance_filing_lapsed": { "last_30_days": 38, "source": "FMCSA" }
  },
  "definition_hash": "sha256:4f2c…",
  "illustrative": true
}

Response

Illustrative values. The response marks itself illustrative so a client cannot mistake an example for live coverage.

Security and behavior

Five rules that do not bend

OAuth client credentials
A partner exchanges client credentials for a short-lived access token. There is no long-lived API key.
Tenant scope
Every token is bound to one tenant and one approved use case. A token cannot read or write another tenant's audience, conversation or outcome.
Idempotency
Write calls require an Idempotency-Key. A repeated key returns the first result instead of creating a second record.
Signed webhooks
Outcome events are signed. A receiver that cannot verify the signature must reject the event rather than trust it.
No bypass
The API cannot skip eligibility. A send requested through the API passes the same gates, in the same order, as a send started in the product.

Access

How partner access is granted

  1. Tell us the use case

    What you sell, which trucking businesses you want to reach and which result counts.

  2. Scope and review

    We agree the tenant, the approved use case and the scopes your token will carry.

  3. Sandbox, then production

    You integrate against illustrative data first. Production access follows the review.

Request partner access

There is no public self-service API today and no self-serve signup for one. A public API is a later release and is not generally available: access is granted to selected partners for an approved use case.