Skip to main content
New releasesImprovementsBug fixesBreaking changes

Messaging

  • Telegram edits, deletion, and typing: Edit a delivered outgoing message’s text or caption, delete it within 48 hours, and show a typing indicator in a private chat. Edits arrive as separate message.update Messages linked to the original by parentMessageId; the original Message stays unchanged. See Send a Message and Set typing in a Space.
  • Telegram albums: Send 2–10 attachments in an album, up to 50 MB in total: mix photos and videos, or send an album of audio files or documents. Each photo can be up to 10 MB. See Send a Message.
  • SMS verification codes: Ordinary verification codes from supported phone-number senders reach your SMS Inbox, message history, and events instead of being filtered. Short-code senders remain unsupported, and WhatsApp Business registration codes stay reserved for setup through Photon. See SMS.
  • SMS activation status: Read detail.activationState to distinguish an activating number from an active one, separately from ownership. The dashboard follows this saved status instead of completing activation on a browser timer; it is not a carrier-readiness check. See SMS number activation.
  • WhatsApp Business disconnection: Disconnect a number even when Meta refuses deregistration, without leaving the Photon removal stuck. The dashboard explains what remains in WhatsApp Manager and the steps to reuse your number. See Disconnecting a number.

Breaking change

  • Message edit content: Replace text.update with message.update and put the complete resulting text or media content in its content field. Update content filters and event readers too; the retired type is no longer accepted. See Send a Message.
  • Reaction content: Remove action from reaction content; that field is now rejected. Reaction removal is represented by message.delete targeting the reaction Message’s ID, rather than action: "remove"; this contract change does not add reaction support to a channel. See Send a Message.

Webhooks and events

  • App event subscriptions: Configure an App’s webhook endpoint and requested event types once, then let each installing organization approve delivery within its chosen projects and permissions. Read the App’s signing-key status and reveal its signing secret to verify deliveries. See Register a developer app and Read an App webhook signing key status.

Organizations and access

  • App project access: Approve an App for All projects, including future projects, or select individual projects. Review update lets you approve changes to an App’s requested access without silently expanding an existing installation. See Approve an app installation.
  • Automatic organization setup: Your first organization is created when you sign up, including outside the dashboard. The dashboard waits for it on Setting up your organization instead of creating it when you open the project picker. See Create a project.

Breaking change

  • Initial organization endpoint: POST /v1/organizations/initial now returns 404. Stop calling it after signup; your initial organization is created automatically. Use POST /v1/organizations when you want to create another organization. See Create an organization.

Billing

  • Promotion codes in checkout: When upgrading an existing messaging subscription, select Add promotion code to preview the discount before you confirm. A code that cannot be used shows its reason without redeeming it. See Preview a project billing change.
  • Discounts and upcoming charges: Organization billing shows Discounts, and subscription terms include the coupons in effect. Billing previews include per-line discountCents and upcomingInvoices; the next charge reflects applicable coupons for resource changes and downgrades as well as upgrades. See Get the organization’s effective billing terms and Preview a project billing change.
  • Dedicated line payments: A dedicated iMessage or WhatsApp line becomes yours and usable after its payment settles. A refused payment fails the purchase with CHARGE_REFUSED instead of leaving you with an unpaid line. See Provision dedicated iMessage line and Provision dedicated WhatsApp line.
  • Billing email recipients: Edit the Recipients row under Billing email, add addresses with Add recipient, and select Save recipients without leaving the page. See Invoices and payments.

Dashboard

  • Resource activity previews: Hover over or focus a supported messaging resource row to see seven days of received and sent activity, with failure marks. The preview refreshes while it is open. See Messaging.
  • Voice-note playback: Play supported iPhone voice notes in their message bubble, including in browsers that cannot play the original CAF file. When the sender’s device supplies a transcript, it appears with the recording; unsupported files keep a download option. See iMessage.

API and SDKs

  • Read an App’s own installation: Call GET /v1/installations/current with installation credentials to read the approved project scope, permissions, and event subscription without organization-wide read access. See Read the credential’s App installation.
  • MCP 0.1.6: The local @photon-ai/mcp server adds listPaymentActions, tool titles, and API reference links. Both the local and hosted servers accept additive response fields and enum values instead of failing with upstream_contract_violation. See Photon MCP server.
  • Expanded API reference: The reference now includes the existing 10DLC brand, verification, campaign, and fee operations, plus project trace, log, and query operations. These are documentation additions, not new endpoint behavior. See List brands and Get the Developer OTel query schema.
  • Billing startup problems: Temporary billing setup states return 503 BILLING_NOT_PROVISIONED or 503 BILLING_ENTITLEMENTS_PENDING, so you can distinguish retryable initialization from a generic upstream failure. See Problem catalog.

Voice

  • Overdue billing: New inbound calls are refused with SIP 403 while the payer is suspended; calls already in progress continue. See Overdue invoices.

Breaking change

  • SIP diagnostic headers: Update parsers from X-Spectrum-* to X-Photon-* for Inbound-Reject, Downstream-Status, Upstream-Status, Upstream-Reject, and Reject-Reason. Their values and meanings stay the same. See Voice.

Docs

  • Message delivery guides: New Webhook and WebSocket guides cover setup, signature verification, retries, ordering, saved cursors, and reconnects, so you can choose and implement the delivery method your application needs.

Bug fixes

  • iMessage links: Incoming text with a rich-link preview no longer disappears. You receive the sender’s text and URL without duplicate preview metadata. See iMessage.
  • WhatsApp Business signup: Meta-provided free numbers, including its +1 555 and +1 711 ranges, no longer fail to save after Meta accepts the signup. Reconnect a signup that failed before this fix. See WhatsApp Business.
  • 10DLC review feedback: Review history shows readable rejection paragraphs and clickable links, and repeated provider updates no longer create the same review entry again. See Fix a rejected 10DLC campaign.
  • Dashboard messaging: Telegram edits update the original bubble without adding another readable message or moving an older conversation to the top. The support launcher no longer covers Send while you compose. See Messaging.
  • Dashboard billing and navigation: Credit balances refresh after plan checkout, and deleting a project no longer briefly shows an error for the deleted project. Project selection also fits tablet and landscape layouts. See Billing and Create a project.
  • Hosted MCP sessions: Connections no longer lose their session as soon as the hosted server idles. See Photon MCP server.
New releasesImprovementsBug fixesBreaking changes

Messaging

  • iMessage replies: Send a message with parentMessageId and it arrives as a native iMessage reply to that message. Replies work in direct and group conversations, on dedicated and shared lines, and for text, single attachments, and attachment groups. Before, these sends failed with 409 SPACE_NOT_SENDABLE. See Send a message.
  • Telegram files, video, audio, and voice notes: POST /v1/projects/{id}/messages to a Telegram Space accepts any single attachment and voice content. Telegram shows each in its native form: JPEG and PNG images up to 10 MB as photos, GIFs as animations, MP4 as inline video, MP3 and M4A in the music player, and any other file as a file card. Voice content in OGG Opus, MP3, or M4A arrives as a voice note. Set telegram.sendAs to "file" to send an attachment as a file card, unchanged. See Send a message.
  • SMS number purchases with no number in stock: A purchase that finds no number fails with NUMBER_INVENTORY_UNAVAILABLE one minute after you request it, instead of searching indefinitely, so you can try another area code or leave the area code out. When a purchase fails, your organization’s Owners and Admins get an email that says what to do next. See Purchase SMS number.
  • iMessage lines without iMessage on their number: When Apple hasn’t registered a dedicated iMessage line’s phone number for iMessage, the line’s iMessage health reads unavailable instead of degraded, and so do new conversations, SMS, and MMS, because nothing can fall back for that number. Sends from the line fail right away with 409 SENDER_NOT_SENDABLE instead of being accepted.
  • Dedicated iMessage and WhatsApp line limit: A project on the Business plan holds up to 50 dedicated iMessage lines and 50 dedicated WhatsApp lines. A request for one more is refused with a 402 ENTERPRISE_PLAN_REQUIRED problem, and a request accepted earlier that reaches the limit fails its operation with the same code. To hold more lines, contact us about an Enterprise plan. When you reach the limit, the dashboard offers a way to contact us. See Provision dedicated iMessage line and Plans and billing.

Dashboard

  • Telegram inbox: A Telegram bot’s page shows its activity and recent messages, and Inbox opens the bot’s conversations. Reply with text or with up to 10 JPEG or PNG photos, 10 MB in total.
  • iMessage first text: On a shared iMessage line, a person you add shows Waiting for first text until they text the line. The agent can reply and start conversations only after that text. The person’s assignment page shows a code to scan with their iPhone to send it.
  • iMessage on phone number: A line’s iMessage health shows whether iMessage works on the line’s phone number.
  • SMS number purchases: Select Cancel purchase to stop an SMS number purchase that is still searching for a number. A purchase that fails shows on the SMS page with what to do next.
  • Mobile numbers for phone verification: Account phone verification accepts only mobile numbers. A landline or VoIP number is refused with phone-number-type-unsupported, and the dashboard asks for a mobile number. See Problem catalog.

API and SDKs

  • Organizations in the SDKs: Version 0.6.0 of the TypeScript, Python, Rust, and Go clients adds 43 operations for organizations and members, invitations, OAuth clients, service identities and their credentials, avatars, and SSO subscriptions. See Organizations and List organizations.
  • MCP server and accepted writes: When the API accepts a write with 202, such as sending a message or provisioning a line, the MCP server returns the result instead of failing with “Request could not be completed”. The hosted server and @photon-ai/mcp 0.1.5 include this.
  • MCP server errors: Tool errors from the hosted MCP server include the problem’s code, status, and title in their text, so clients that read only text see why a call failed.
  • Failed operations return their problem: When an operation fails, its error is the full problem for its code, the same object the endpoint returns when it rejects a request: type, title, status, code, and detail, plus remediation when there’s a next step and typed fields such as reason on ENTITLEMENT_REQUIRED. code keeps its value, so code that branches on it keeps working. Each endpoint that starts an operation lists the codes it can fail with. See Get operation.
  • Larger telemetry queries: POST /v1/projects/{projectId}/metrics/query and the dashboard’s activity views read up to twice as much data per query, so queries on busy projects return query-resource-limit less often.

Breaking changes

  • Dashboard-only operations removed from the SDKs: Version 0.6.0 of the clients removes getAccountOnboarding, updateAccountOnboarding, completeAccountOnboarding, createOrganizationSetupIntent, startAccountPhoneVerification, confirmAccountPhoneVerification, beginOrganizationSsoAdmission, beginOrganizationAuthentication, beginOrganizationClosureAuthentication, beginInvitationSso, connectWhatsappBusiness, and getWhatsappSignupConfig. Their endpoints, such as GET /v1/account/onboarding and PUT /v1/account/phone, also left the API reference. These operations accept only a dashboard session and have refused API credentials since October 17, so remove any calls to them before you upgrade.
  • SMS removed from filtered verification codes: The filtered verification code endpoints, such as GET /v1/projects/{id}/platforms/filtered-otp, accept platform=imessage or platform=whatsapp. platform=sms returns 422, and lists and counts no longer include codes from SMS numbers, so remove platform=sms from your requests. The dashboard no longer shows filtered codes on SMS number pages. See List filtered verification codes.

Webhooks and events

  • Email sending paused and resumed: Subscribe a webhook destination to platform.sending.paused and platform.sending.resumed to learn when email sending for your project pauses or resumes. The event’s reason is reputation_policy or operator_action. See List webhook event types and Create webhook destination.

Billing

  • Pending payments: When your bank asks you to confirm a payment, such as a 3D Secure check, the payment shows under Pending payments on your organization’s billing and invoices pages and on the project’s billing page. Select Confirm to complete it. What the payment is for stays pending until you do. GET /v1/organizations/{organizationId}/billing/payment-actions lists the same payments. See List payments to confirm and Invoices and payments.
  • Promotion codes: Pass promotionCode to POST /v1/organizations/{organizationId}/billing/projects/{projectId}/purchase to redeem a code with an upgrade or a first plan. A refused code fails the operation with promotion_code_rejected and changes nothing. Coupons the project already has stay and stack. See Change plan.
  • Plan charges: In a project’s billing, Compare plans in Messaging Plans opens a page that lists each plan’s price, fixed charges, and usage charges.
  • Credit balance: Owners and admins see the organization’s credit balance on its project picker, with a link to the Credit page.

Docs

  • 10DLC campaign review guides: New guides cover brand verification, opt-in, privacy policy and terms, prohibited content, sample messages, use cases, and carrier rejection codes. Help links in 10DLC campaign feedback now point to these guides. See 10DLC.
  • SMS best practices: SMS best practices covers short codes, verification-code filtering by line type, and using Photon numbers with third-party services.
  • MCP server: Photon MCP server shows how to connect Claude Code, Cursor, VS Code, Codex, Claude, ChatGPT, and other clients, and how to run the server locally.
  • Enterprise plan: Plans and billing describes the Enterprise plan for projects that need more than 50 dedicated lines.

Bug fixes

  • Voice: When an AI agent on ElevenLabs or Retell ends an inbound call over TLS, the caller’s side of the call ends too. Before, the caller stayed connected until they hung up.
  • Billing: Invoice lists that include a usage threshold invoice load again instead of failing with 502. When your bank declines the payment for a plan change or purchase, the operation fails within about 30 seconds instead of up to 5 minutes.
  • Phone verification: A correct code is accepted after your first code expired and you asked for a new one.
  • Dashboard: Clicking the Requested permissions title on New app, New service identity, or Create API key no longer selects or clears every permission. The project picker dialog’s settings action reads Settings, so it fits. The line Support dialog is titled “Contact Photon support”, and its Slack link stays available while your shared channel is being set up or needs attention. Shared iMessage and WhatsApp Personal setup steps fit a phone screen. Requests that get no answer from the network retry before they fail, and pages that your browser translates no longer break.