API Changelog

Track changes, new features, and updates to the LogTalk API. Subscribe to the changelog RSS feed to stay updated.

Current Version: v1

The LogTalk API is currently at version 1. All endpoints are prefixed with /v1/. We follow semantic versioning and will maintain backwards compatibility within major versions.

Releases

v1.2.0January 18, 2026
Added
  • Scripts API - Generate and preview scripts before converting to audio/video
  • Two-step workflow with POST /v1/scripts and POST /v1/scripts/{id}/convert
  • Script expiration after 2 hours
  • word_count and context_used in script responses
Improved
  • Idempotency key validation with better error messages
  • Request timeout increased to 90 seconds for wait=true
v1.1.0January 10, 2026
Added
  • Usage endpoint (GET /v1/usage) for monitoring quota and API requests
  • Rate limit headers on all responses
  • Webhook retry policy with exponential backoff
  • quota.warning and quota.exceeded webhook events
Improved
  • Better error messages with documentation URLs
  • Pagination with cursor-based navigation
Fixed
  • Idempotency key conflict detection for edge cases
v1.0.0December 20, 2025
Added
  • Initial public API release
  • Conversions API (POST, GET, DELETE /v1/conversions)
  • API key authentication with lt_live_ and lt_test_ prefixes
  • Synchronous audio generation
  • Asynchronous video generation with polling
  • Per-request webhooks with HMAC-SHA256 signatures
  • Idempotency keys for safe retries
  • Organization-scoped API access

Versioning Policy

The LogTalk API follows semantic versioning:

  • Major versions (v1, v2) - May include breaking changes. Old versions are supported for at least 12 months after a new major version is released.
  • Minor versions (1.1, 1.2) - New features and improvements. Fully backwards compatible.
  • Patch versions (1.1.1) - Bug fixes only. Fully backwards compatible.

Breaking Changes

We consider the following to be breaking changes:

  • Removing an endpoint
  • Removing or renaming a request parameter
  • Removing or renaming a response field
  • Changing the type of a field
  • Adding a new required parameter
  • Changing error codes for existing scenarios

The following are not considered breaking:

  • Adding new optional parameters
  • Adding new fields to responses
  • Adding new endpoints
  • Adding new error codes
  • Adding new webhook event types
  • Changing error messages (codes remain stable)

Deprecation Notices

There are currently no deprecated features in the API.

When features are deprecated, they will be announced here with a minimum 6-month notice period before removal.

PreviousExamples