Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Technical Question: Coexistence (CoEx / Embedded Signup) Support in Cloud API v2.3.7 vs v2.4.0

Open
#2,738 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
api, backend

Research direction

The issue asks about Coexistence (CoEx) and Embedded Signup support in Cloud API versions 2.3.7 vs 2.4.0. To research, examine the source code for version 2.3.7 and the 2.4 release candidates for references to CoEx flows, embedded signup, or related configuration. Check API documentation and changelogs for feature announcements. Determine if the feature is implemented and how it affects connection behavior between a physical phone and the Cloud API.

Written by the indexing model from the issue text.

Description

Hello team,

I need to make a definitive architectural and risk assessment for a production environment, and I would appreciate your official insight as project maintainers.

After analyzing the source code of the current stable version (2.3.7), we couldn't find any explicit references to the Coexistence (CoEx) flow or Embedded Signup for the official Cloud API. We noticed that references to branch 2.4 are currently marked as Release Candidates (rc1 / rc2).

Our technical questions for this decision are:

  1. If we connect an active WhatsApp Business number currently running on a physical phone using the official Cloud API channel in the stable version 2.3.7, will the phone app disconnect immediately (Meta's default behavior without CoEx)?
  2. Is official support for keeping both the physical phone and the Cloud API connected simultaneously (CoEx) strictly tied to the final stable release of version 2.4.0?

Thank you in advance for clarifying this so we can align our handoff documentation with full technical safety.

Dominant language
TypeScript
Stars
9.6k
Forks
7.3k
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evolution-foundation/evolution-api

All issues in evolution-foundation/evolution-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.