Developers

Platform APIs

Use tenant isolation, API keys or OAuth, and versioned routes. Examples below match implemented endpoints — not a fictional catalog.

Base URLs

v1: https://trustics.loginics.com/api/v1

v2: https://trustics.loginics.com/api/v2

OpenAPI (Scramble) · Health

Authentication

X-Tenant-Id: your-tenant-id
X-Api-Key: ts_your_api_key

# Sanctum
POST /api/v1/auth/login
Authorization: Bearer {sanctum_token}

# OAuth2 client credentials
POST /oauth/token
Authorization: Bearer {access_token}
X-Tenant-Id: your-tenant-id

Constraints: tenant isolation, authorization on each resource, rate limits via throttle:api, JSON error envelopes, and field-level Passport visibility.

Implemented v2 platform routes

Organization

GET /api/v2/organizations/{id} — identity, industry contexts, identifiers, Passport summary.

Contextual TrustScore

GET /api/v2/trustscore/{entityId} — industry-aware score, dimensions, and explanation.

Participants

GET/POST /api/v2/organizations/{organizationId}/participants · GET/PATCH/DELETE /api/v2/participants/{id}

Digital Passport

GET /api/v2/passports/{passportNumber} — permitted Passport fields for the calling tenant.

Consent-controlled share

POST /api/v2/passports/{passportNumber}/shares — create a time-bound share token.

v1 compatibility

Logistics and credit workflows remain available. They are not the only way to use Trustics.

  • GET /api/v1/organizations/search and GET /api/v1/organizations/{id}
  • GET /api/v1/trustscore/{entityId}, history, explanation, generate
  • POST /api/v1/ratings and POST /api/v1/ratings/{ratingId}/dispute
  • POST /api/v1/credit/{entityId}/report and PDF export
  • Webhooks: GET /api/v1/webhooks/event-types, CRUD under /api/v1/webhooks
  • Trustics AI (capability-specific, no generic prompt): POST /api/v1/ai/conversations, POST /api/v1/ai/explanations/trustscore, POST /api/v1/ai/explanations/passport, POST /api/v1/ai/analytics, POST /api/v1/ai/navigation, POST /api/v1/ai/report-drafts, GET /api/v1/ai/jobs/{jobId}
  • Platform resources: credentials, evidence, relationships, activities, reporting assignments, trust reports, passport consents
# Agriculture cooperative Passport
curl -s \
  -H "X-Tenant-Id: your-tenant-id" \
  -H "X-Api-Key: ts_your_api_key" \
  "https://trustics.loginics.com/api/v2/passports/{passportNumber}"

# Filter a score by industry context on the organization record
curl -s \
  -H "X-Tenant-Id: your-tenant-id" \
  -H "X-Api-Key: ts_your_api_key" \
  "https://trustics.loginics.com/api/v2/trustscore/{entityId}"

# Consent-controlled share (healthcare professional, no clinical fields)
curl -s -X POST \
  -H "X-Tenant-Id: your-tenant-id" \
  -H "X-Api-Key: ts_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"showScore":true,"showCredentials":true,"showEvidence":false}' \
  "https://trustics.loginics.com/api/v2/passports/{passportNumber}/shares"

Sandbox and Trustics AI

The synthetic tenant trustics-platform-demo is the sandbox. Seeded personas use password demo12345. Demo mode never bypasses authorization or tenant isolation. AI answers are retrieved through the same tools used in production; scenario catalogs do not contain canned answers.

  • Consent-authorized Passport access: POST /api/v1/passport-consents and DELETE /api/v1/passport-consents/{consentId}
  • Webhooks are signed, retryable, and carry a correlation ID. Payloads stay minimal; fetch records through authorized APIs.
  • Long-running analytics may return 202 with GET /api/v1/ai/jobs/{jobId}. Job results re-check authorization on read.
  • Clients must not send system_prompt or arbitrary tools. The backend selects tools from the acting principal’s permissions.
  • OpenAPI is published at the docs URL above. Examples on this page match implemented routes.

Trustics AI can navigate, explain, draft, and analyze. It does not submit reports, change TrustScores, publish configuration, resolve disputes, or make high-impact decisions.