Pier: Mobile & Auto insurance — API integration

Deliverables checklist

• OpenAPI 3.1 specification mapped to OPIN resource models
• Protocol and authorization flow report (token, refresh, certificate pinning)
• Runnable source for policy, claim, and reimbursement APIs (Python & Node.js)
• Postman / Insomnia collections plus pytest / Jest test harnesses
• LGPD & SUSEP compliance notes (consent, retention, data-minimization)
• Operations runbook: rate limits, retries, idempotency keys, error taxonomy

Engagement options

• Source-code delivery from $300 — runnable code and full docs handed over; you pay only after acceptance.
• Pay-per-call hosted API — we operate the integration and bill per successful call, with no upfront fee.
• Hybrid — start with hosted endpoints, migrate to in-house deployment once volume stabilizes.

1. Broker-channel policy sync

Pier expanded into the broker channel in 2024 and now works with partners such as SegPartners, Klubi and Cota Fácil, with more than 1,500 broker partners registered. A nightly job pulls /policies?updatedSince=… and pushes new and renewed contracts into the broker’s CRM, mapping Pier’s product codes to the broker’s internal commission table.

2. Pier Bolt reimbursement webhook

Pier Bolt settles 30% of smartphone claims in under one second. A webhook subscriber receives claim.reimbursement.completed events, posts the corresponding ledger entries to the carrier’s ERP, and triggers a CSAT survey via the marketing automation tool — all within the same idempotent request flow.

3. OPIN data-portability flow

When a Pier customer authorizes a competing insurer to import their loss history, the consent is granted in the receiver’s app, transported through the OPIN directory, and resolved against Pier’s resource server. Our integration handles the FAPI Brasil security profile, dynamic client registration, and the standard damages and person APIs.

4. Embedded auto insurance at point of sale

A car dealer in Belo Horizonte offers Pier auto insurance at signing. Our SDK calls a quote endpoint with the FIPE code and proposed coverage, surfaces the monthly premium, and posts the signed proposal back to Pier. The contract appears in the customer’s app within minutes, ready for inspection booking.

5. Loss-ratio analytics for reinsurance

A reinsurance partner consumes anonymized claim and premium streams to compute book-level loss ratios per device model and FIPE category. The pipeline runs on hourly windows, joins Pier data with NPS feedback, and powers the underwriting team’s pricing review.

Authorization handshake

POST /api/v1/pier/auth/token
Content-Type: application/json

{
  "grant_type": "password",
  "username": "user@example.com",
  "device_id": "a1b2c3-...-e5f6",
  "scope": "policies claims reimbursements"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_3d4f...",
  "expires_in": 3600,
  "token_type": "Bearer",
  "scope": "policies claims reimbursements"
}

Policy & claim retrieval

GET /api/v1/pier/policies?status=active&product=auto
Authorization: Bearer <ACCESS_TOKEN>
X-Idempotency-Key: 7b14...

200 OK
{
  "items": [{
    "policy_id": "POL-882134",
    "product": "auto",
    "vehicle": {"fipe": "004128-7", "plate": "ABC1D23"},
    "premium_brl": 189.90,
    "status": "active",
    "addons": ["glass", "mirrors", "rental_car"],
    "started_at": "2026-02-14T00:00:00-03:00"
  }],
  "next_cursor": null
}

Pier Bolt reimbursement webhook

POST https://yourapp.example.com/webhooks/pier
X-Pier-Signature: t=1714..., v1=8c3...

{
  "event": "claim.reimbursement.completed",
  "claim_id": "CLM-552310",
  "policy_id": "POL-114209",
  "amount_brl": 2899.00,
  "settlement_method": "PIX",
  "latency_ms": 870,
  "occurred_at": "2026-05-07T14:32:11Z"
}

// Verify HMAC, ack with 200 within 5s,
// or Pier retries with exponential backoff.

Error taxonomy & retries

All endpoints return RFC 7807 problem documents. Transient failures (HTTP 502/503/504, plus rate-limit 429) are retried with jittered exponential backoff up to five attempts; 4xx validation errors short-circuit and surface a machine-readable code. Idempotency keys prevent duplicate writes when a network blip splits a request.

SUSEP, OPIN, and LGPD

Pier was the first insurtech to graduate from the SUSEP regulatory sandbox and now operates as a full digital insurer. Our integrations therefore align with the OpenInsurance Brasil (OPIN) framework coordinated by SUSEP, including the FAPI Brasil security profile, dynamic client registration, and the standard consent lifecycle. On the privacy side, we follow LGPD (Lei Geral de Proteção de Dados) for data minimization, retention, and right-to-erasure flows, and we never persist plain-text CPFs or claim photos outside the customer’s tenant.

Authorization & auditability

Every call is mediated by an authorization scope, a per-tenant API key, and a signed audit log. Reimbursement and policy-mutation calls require a fresh user token (re-authentication if the access token is older than 15 minutes), and webhooks are signed with rotating HMAC secrets so downstream systems can prove provenance during a SUSEP inspection.

About us

OpenFinance Lab is an independent studio focused on fintech, insurtech, and open-data API integration. Our engineers come from banks, payment networks, mobile reverse engineering, and cloud platforms, and we have shipped insurance integrations under SUSEP, OPIN, FAPI Brasil, LGPD, and equivalent rules in Mexico, Spain, and the UK.

• Insurance, payments, digital banking, and cross-border clearing
• Mobile protocol analysis on Android and iOS, including certificate pinning and obfuscated SDKs
• Custom Python, Node.js, and Go SDKs with full test harnesses
• End-to-end pipeline: scoping → protocol analysis → build → validation → compliance review
• Source-code delivery from $300 — runnable code with documentation; pay only after acceptance
• Pay-per-call hosted API — usage-based billing, no upfront commitment

Contact

For quotes or to submit your target app and requirements, open our contact page:

Contact page

Engagement workflow

1. Scope confirmation — which products (smartphone, auto), which flows (policy, claim, reimbursement), and which side of OPIN.
2. Protocol analysis & API design (2–5 business days)
3. Build and internal validation against sandbox or recorded fixtures (3–8 business days)
4. Documentation, sample requests, and pytest / Jest tests (1–2 business days)
5. Typical first delivery: 5–15 business days; OPIN certification adds 1–2 weeks.

FAQ

What do you need from me to start a Pier integration?

How long does a typical Pier integration take?

How do you stay compliant with SUSEP and OPIN rules?

Can you cover both smartphone and auto insurance flows?