What's new in the next generation API?

Starting December 1, 2025, we'll be releasing the next generation of our API to public beta. This is something we've been actively working on for the past year.

https://beta.dashboard.loopmessage.com/auth/login

https://docs-beta.loopmessage.com

Why did we work on the new API?

We first began working on the iMessage API five years ago. Initially, when developing this API, we pursued specific goals that were relevant 5y ago. However, over the past few years, the market has undergone numerous changes, and we realized that a complete redesign of our backend would eventually be necessary.

Furthermore, five products operated under the LoopMessage brand that were unrelated to each other, which was confusing to some new customers.

In January 2025, we began working on separating each product into separate brands. Each of these products now has its own separate backend and frontend with its own microservices. Previously, our API endpoints from all products operated as a single monolithic project, with a dozen microservices that also interacted with the API.

For the iMessage API, we completely redesigned the backend and frontend from scratch, as well as redesigned many architectural issues that were not obvious five years ago. We also tried to incorporate into the new architecture the customer requests we had accumulated over the past few years.

What does this mean for current customers?

For now, we plan to maintain the legacy API until the majority of our customers migrate to the new generation. We plan to do it in a few iterations during the winter.

December 2025 - public beta

January 2026 - stop accepting new sign-ups through the old backend. All new users will be able to sign up only through the new dashboard.

February 2026 - moving all other users to the new backend with saving maximum backward compatibility.

What are the major changes?

1) We're changing our pricing model. Previously, you paid for a dedicated sender name plus each API request. Now, we offer unlimited messaging with a limit on the number of contacts.

2) We're moving from our current payment gateway, Paddle. Your statements will now display "Loop" instead of Paddle. This was necessary because, due to Paddle's restrictions, we were unable to add the ability to make purchases through our API.

3) We plan to increase the number of channels we will work with. We're already working on adding new channels: RCS and WhatsApp. So you can use one unified API and phone number for all your users. RCS should be released during Dec 2025, WhatsApp in Jan 2026.

4) Registering phone numbers in different regions

5) Implementing integrations with no-coding tools and CRMs.

What are the breaking changes in the new API?

https://docs-beta.loopmessage.com

Although over 90% of our new backend code was re-designed from scratch, we've strived to keep max backward compatibility. However, you'll still need to make some minor changes during the migration.

1) Changed the API host.

2) The sender_name parameter will now require you to specify an ID instead of your sender's email address. The same will apply to webhooks, now you should rely on the ID instead of the name.

3) Error codes have been completely redesigned. If you were relying on specific error codes, you'll need to change them.

4) Since the new API generation is a separate backend with a separate database, message history or active contacts will not be migrated. We're currently working on implementing such synchronization, but this could be challenging due to some large-scale customers have millions of messages per month.

How to migrate to the new API?

All you need to do is sign in to the new dashboard:

https://beta.dashboard.loopmessage.com/auth/login

At this point, the new backend will take all your account information from the previous backend, and everything will be transferred immediately.

You just need to select a new plan for each of your sender names, and then you can start using the new API.

Then you should use our new API doc:

https://docs-beta.loopmessage.com

Can I use the new API in production?

Over the past 6 months, we have been running a lot of tests with some of our customers using the new API in private beta.

However, there may be issues with the frontend. We'd be happy if you could report any issues in the public beta so we can fix them asap.

What will happen with my credits and my current payments for sender names?

For your current sender names, we'll prorate/refund your last payment.

If you have more than 100 credits, please contact support, and we'll prorate or refund payments.

What will be with old payment model?

Effective Dec 1, 2025, we're leaving only ConversationKit plans, where you can purchase sender name + credits. All credits are still shared among all your sender names.

Since Jan-Feb 2025, we plan to disable the feature for buying new message credits for legacy payment plans.

Once we fully switch all requests from the legacy backend to the new generation, users who haven't changed their plans will be auto-switched to the new default plans with "unlimited messaging".

Updated on: 02/12/2025