Skip to main content
​

​
Batch v2 & Files API

A new generation of the Batch API is available, improving flexibility while also improving security and throughput. Uploads move from one-file-at-a-time batch inputs to multi-file upload sessions with MD5 integrity checks. Batch executions follow that move, allowing multi-file inputs that now support Parquet extensions, deprecate JSONL and keep the support for CSV for low complexity schemas.
  • POST /v2/api/files/upload — request upload URLs for one or more files.
  • GET /v2/api/files — list uploaded files and their metadata.
  • POST /v2/api/batches — start a batch prediction for one or more files.
  • GET /v2/api/batches/{id}/result — retrieve a download URL or a URI path to access your results.
The v1 batch and batch-inputs endpoints are now deprecated, they remain available for backward compatibility and will be sunset soon.Migration guide: Migrating to Batch v2. See also Batch Inference.
​

​
Webhooks

Real-time HTTPS callbacks are now available across the platform. Configure endpoints from Platform → Alerts → Webhooks with per-endpoint event subscriptions, HMAC signing, and a built-in delivery history with replay.Event catalog spans batches (batch-request, batch-lifecycle, batch-result-download, …), model versions (model-version-promotion, model-version-activation, …), workspace, and API keys. See Webhooks.

​
Workspace Notifications

The same event catalog now powers human-facing notifications. Subscribe to any event for delivery via email and in-app channels from Settings → Workspace → Notifications. See Notifications.

​
Audit Logs

Expanded audit coverage for organization access control and user lifecycle events. The dashboard now tracks the full lifecycle of invitations, membership changes, authentication activity, and organization-level updates.Invitations
  • Invite created, accepted, and revoked events
  • Full traceability from invite sent to user onboarded
Membership
  • Member added, role updated, and member removed
  • Organization membership creation, updates, and deletion
Organization & Sessions
  • Organization configuration changes
  • User creation, updates, and deletion
  • Login and session creation events
All events are visible in the dashboard under Observability → Audit, giving your compliance and security teams a complete view of who did what and when.
​

​
Data Contract Enforcement

Data contracts are now enforced in production, structured in two layers: ingestion and transformation.The ingestion layer validates every file against the agreed schema. Any deviation triggers an automatic notification. When discrepancies occur, they are classified either as a new contract version or as a data error — ensuring clear ownership and faster resolution between your team and ours.

​
Prediction Audit Events

Audit visibility is now available in the dashboard for prediction consumption:
  • Prediction consumption via API
  • Prediction consumption via Dashboard
  • Batch prediction start (API and Dashboard)
  • Batch prediction completion (API and Dashboard)
These events allow you to monitor usage and execution lifecycle directly from the UI. Navigate to Observability → Audit to review activity. Additional audit events will be progressively added in future releases.

​
Graph Foundation Model v2.6

The Graph Foundation Model has been updated to version 2.6.The underlying graph now incorporates additional data sources and new types of relationships, resulting in a more connected graph. No new data fields were introduced, but the model now more effectively leverages information that was already available — improving overall consistency and unlocking new relational signals across entities.
​

​
Dashboard

New Avra dashboard available for all organizations.
  • Unified navigation for models and batches
  • Role-based visibility for billing, audit logs, and API credentials
  • Multiple workspaces support
  • Streamlined invite flow with enforced SSO where configured
Rollout is complete; existing users will see the new experience on next sign-in.
​

​
API

Improved GET /v1/api/models/{model_id}/versions/{version_id} to return the model’s full input/output schema with metadata about each field. This enables dynamic form generation, automated validation, and programmatic discovery of model capabilities in your integration code.
​

​
Platform Migration

We have evolved our platform to a new generation, designed for greater reliability, lower latency, and a more scalable and extensible architecture. This transition unlocks a broader range of data integration possibilities and enables us to deliver tailor-made AI models that adapt to each customer’s unique context.The following legacy endpoints have been sunset:
  • POST /v1/api/risk_score
  • POST /v1/api/entities/context/contact
  • POST /v1/api/entities/context/transaction
  • POST /v1/api/entities/context/invoices
These endpoints now return 410 Gone. All new integrations should use the model registry prediction endpoints.
Migration guides: Prediction Platform | Data Integration

​
Documentation

Documentation serving platform migrated to Mintlify for improved user experience.
  • Restructured guides with business-first approach while preserving technical depth
  • Enhanced integration documentation with clearer customer journey paths