Skip to content

Release notes

Release Notes tell you what’s new in API. As always, we welcome your feedback.

  • New Endpoint: /invoices — List and view invoices with filtering by status, payment type, date range and amount range. Each invoice includes a downloadable PDF and related credit note links.
  • New Endpoint: /credit_notes — List and view credit notes with the same filtering capabilities as invoices. Each credit note links to its parent invoice.
  • New Endpoint: /payments — Create new payment attempts using saved credit/debit cards or SEPA mandates. List and view payment history with detailed status tracking, amounts, fees and VAT breakdowns. When 3D Secure authentication is required, a redirect_url is returned for browser-based completion.
  • New Endpoint: /payment_methods — Retrieve the authenticated user’s available payment methods: stored credit/debit cards and active SEPA mandates. Use the returned IDs to create payments via POST /payments.
  • New Endpoint: /invoices/{id}/pdf and /credit_notes/{id}/pdf — Download PDF documents for invoices and credit notes.
  • New API key role Payments — Endpoints /invoices, /credit_notes, /payments and /payment_methods require a dedicated Payments API key for access.
  • New Endpoint: /pricelist/{country}: Public endpoint to download SMS price lists. Returns prices for all available service routes (direct, text2speech, economy, pro) in JSON, Excel or CSV format. Supports currency filtering (EUR, CHF) and multi-language country names (en, de, es, pt, pl). Includes country-specific sending requirements. No authentication required.
  • New Endpoint: /me/pricelist/{country}: Authenticated endpoint to download a personalized price list with user-specific SMS rates. Returns a single price per service based on the user’s price level. Currency is taken from the user’s account settings, language defaults to the user’s profile language. Available in JSON, Excel or CSV format.
  • New Endpoint: /verify_codes: added a dedicated REST API for creating and managing one-time verification codes (OTP). Supports multi-step routing strategy (Telegram, Voice call, SMS) with automatic fallback and timeout control.
  • New property attempts_count_max for SMS endpoint: Control the maximum number of delivery attempts for voice services (text2speech, text2speech_ssml). Accepts values 1, 2, or 3 for voice services, allowing fine-grained control over call retry behavior. Must be null for standard SMS services.
  • Expanded voice message language support from 5 to 20 languages. Users can now set voice_lang to any of the following European languages: EN, DE, FR, IT, ES, PL, NL, RO, PT, CS, HU, SV, DA, FI, SK, HR, TR, RU, BG, UK.
  • Improved automatic language detection. Switched from phone prefix-based to AI-powered content analysis using message text when voice_lang is null.
  • New webhook events for phone subscription management: phone.subscribe and phone.unsubscribe
  • Added IP address v6 support for the endpoint POST /fraud-checks
  • New Endpoint: /blocked_numbers: added a dedicated REST API for managing blocked phone numbers in SMS campaigns. The endpoint provides complete CRUD functionality for maintaining a centralized blocklist of phone numbers that should not receive SMS messages.
  • Response headers - All API responses now include a unique X-LOX24-REQUEST-ID header for support and tracking purposes
  • OpenAPI specification reorganized - Major restructuring with multiple semantic errors fixed
  • Documentation rendering - Replaced dynamic OpenAPI JSON browser rendering with static compiled HTML pages
  • Webhooks documentation - Added comprehensive webhooks description and implementation details
  • New webhook events for Email to SMS parsing: sms.email.parsing.success and sms.email.parsing.fail
  • Added Phone’s read-only properties subscribed_at, unsubscribed_at and unsubscribed_reason (see Phone API
  • The Incoming SMS list by default is ordered by decreasing values of the received_at field.
  • Added the ability to authenticate using the new version of the API key with a single header X-LOX24-AUTH-TOKEN, header X-LOX24-AUTH-CLIENT-ID is deprecated and not recommended for use.
  • Voice messages. Added voice_lang property to SMS and Bulk request/response objects.
  • Temporary block IP address after multiple invalid authentication attempts.
  • Added ability to send SMS with additional data which will be send back to DLR endpoint.
  • Added sample code per Phones and Groups endpoints.
  • Added sample code in GoLang, Java and Python.
  • Added boolean filter of Bulks list GET /bulks by the property is_dryrun.
  • Added timestamp property balance_changed_at to the endpoint GET /me.
  • Created endpoints GET /incomings and GET /incomings/{id} to retrieve info about incoming and related SMS.
  • Enabled DLR report webhook on POST /sms/dryrun request.
  • Added exact filter by key_id on GET /bulks and GET /sms.
  • Added sample code in PHP, C# and Javascript per /sms, /bulks and /incomings endpoints.
  • Added section Inbound SMS and Reply-SMS about incoming SMS.
  • Fixed a bug related to storing the ip address, date and time of the last API key use
  • The feature that helps you make bulk sms in just one HTTP request:
    • with text template and contact groups
    • preliminary calculation of the cost of bulk SMS
    • fast server response and asynchronous processing
    • bulk SMS cancellation option even during processing
  • New endpoint POST /groups/{id}/phones/batch
    • combine multiple POST /groups/{id}/phones to an one request
  • Implemented filters GET /sms by the property bulk
  • Implemented filters GET /bulks by the property source
  • Added API key ID info to sms and bulks responses
  • Added property price to SMS response object
  • Authorization parameters description in the API documentation
  • API v2.0 has been developed in accordance with industry standards to make integration as easy as possible. In addition, you can now transmit large quantities of SMS with one query and retrieve detailed information about the messages at any time.

  • The extensive group functionality allows you to manage your mailing lists in our high-performance cloud and thus save your own resources. All this is still compliant with European data protection standards and the German Telecommunications Act.

You can find the new API description at https://doc.lox24.eu/