Sense Street Batch API

name: Sense Street Batch API
description: The enterprise REST API. Callers upload files of broker conversations for asynchronous processing
  and retrieve the extracted RFQs once parsing completes, or call the prediction operations synchronously
  against a single conversation or chat snippet. Bond reference data and electronic RFQ records are uploaded
  through the same surface for instrument resolution and reconciliation. Authentication is a client-signed
  RS256 JWT bearer assertion with the caller's public key sent in an X-key header; there is no OAuth and
  no scope surface.
humanURL: https://docs.sensestreet.com/batch-api
baseURL: https://{tenant}.api.sensestreet.com/api/v1
tags:
- Batch Processing
- Conversation Intelligence
- RFQ Extraction
properties:
- type: Documentation
  url: https://docs.sensestreet.com/batch-api
- type: Authentication
  url: authentication/sense-street-authentication.yml
- type: Conventions
  url: conventions/sense-street-conventions.yml
- type: DataModel
  url: data-model/sense-street-data-model.yml
- type: ErrorCatalog
  url: errors/sense-street-problem-types.yml
- type: MCPServer
  url: mcp/sense-street-mcp.yml
x-base-url-note: 'The host is per-tenant and issued at onboarding. Evidence: the wildcard certificate
  Sense Street serves carries the SANs *.api.sensestreet.com and *.api.test.sensestreet.com; the first-party
  SDK hard-codes the JWT audience claim aud=api.sensestreet.com and requires the customer to pass api_url
  because there is no default; and the bare host api.sensestreet.com has no A record. The /api/v1 path
  segment is appended by the SDK itself and answers live (HTTP 401, "Invalid or missing token") on the
  Sense Street portal host.'