💡 Feature Requests

As a Salesmsg user integrating via the API and webhooks, I'd like a reliable way to connect an MMS attachment to the message and conversation it belongs to. Right now, the incoming/outgoing MMS webhook gives us message.id and conversation_id, but GET /attachments/recently returns attachments with no message_id, conversation_id, or created_at on them. There's no way to match an attachment back to the webhook event that triggered it, especially when multiple MMS messages come in around the same time. It would help to have either: An endpoint to fetch attachments filtered by message_id An endpoint to fetch attachments filtered by conversation_id Or simply have the webhook payload include the attachment URL/ID directly alongside message.id Any of these would let us reliably sync MMS attachments into our own systems (in our case, Monday.com ) without guessing which attachment belongs to which message.

I would like to quickly be able to check the status of Salesmsgs API. This will help to quickly determine if the server is down or if the error is on my end.

As a Salesmsg user integrated with the Salesmsg API, I'd like to use "Stop On Response" for a programmed Scheduled message, so that I could use this feature programmatically.

Currently, the API only supports endpoints for broadcasts, but there are no available endpoints to create or manage campaigns programmatically. It would be extremely helpful to have API support for campaigns, including the ability to create, update, and trigger them. This would allow for better automation, integration with external systems, and more flexibility for users who rely on workflows beyond standard broadcasts. This would significantly improve the API’s functionality and expand automation capabilities.

As a Salesmsg user integrating my own software with Salesmsg, I'd like a version of my Salesmsg account that I could use with the API as a Sandbox, so that I could verify my system works before I use it on my Salesmsg account with real data.

It would be massively helpful to have the ability to select phone numbers to send SMS texts from. This would apply to workspaces with multiple numbers, and only one user. The current user interface does not allow for phone numbers to be unassigned from workspaces with a single user. We are only able to pass the team_id as a parameter from the phone call, thus having no control over which phone number we are sending texts from. Thank you.

As a Salesmsg user, I'd like to be able to use an outside system like a CRM to post conversation notes to a timeline. Aircall SIP trunk use case: I'd like to post Aircall call events from a SIP trunk number back to Salesmsg as a timeline entry.

As a user who builds integrations with their Salesmsg account, I'd like a way to send a long URL to our short URL endpoint and have a shortened version returned, so that I could use the feature from my desired platform.

As an Organization Owner who uses the Salesmsg API, I'd like analytics accessible via our API so that I could more easily access that information.

As an advanced user, I'd like Salesmsg to offer API keys for server to server integration, so that I can integrate with Salesmsg in the way I'd like to