API
Your connected numbers and channels from your own backend.
Use your own connected numbers and channels from your backend: read their status and sending health, get their credentials, decide where messages go, and hear when something changes. Automations and scheduled posts too. Messages never pass through EasyCoexistence: your backend sends through Meta with the number's own token, and Meta delivers incoming messages straight to your URL.
Building for other businesses? The Partner API is the same API and key, plus hosted connect links for your customers, external_ref and their events.
Start
- Get a key. Dashboard → Developers → Create key, or ask your AI assistant connected to EasyCoexistence (
create_api_key). It starts withec_live_, is shown once and belongs on your server only, never in a browser or an app. One key per account. - Connect. Numbers and channels are connected in the dashboard (New connection) and show up here.
- First call.
curl https://easycoexistence.com/api/v1/connections \
-H "Authorization: Bearer ec_live_..."
{
"data": [
{ "id": "6f1c…", "phone": "+55 11 9…", "name": "Bloom Café", "status": "connected", "sending_health": "AVAILABLE", "token_ready": true, … }
]
}From there: Get a number with credentials=1 for the token to send with, Where messages go to receive the messages, and Set the events URL to be told when the number drops or gets blocked.
Using a coding agent?
Give it this prompt. It reads the text version of these docs and does the steps above in your project.
Add the EasyCoexistence API to this project. Read https://easycoexistence.com/docs/api/llms.txt first and follow it.
1. Read the API key from the EASYCOEXISTENCE_API_KEY environment variable. Never hardcode it or commit it. Send it as "Authorization: Bearer <key>" on every request to https://easycoexistence.com/api/v1.
2. List the numbers with GET /connections and show me each one's phone, status and sending_health.
3. Get the credentials of the number I pick with GET /connections/{id}?credentials=1 and store phone_number_id and access_token on my side.
4. Set where incoming messages go with PUT /connections/{id}/webhook, using an https URL with a long random secret in its path, and verify_token.
5. Send a message through Meta directly: POST {credentials.send_endpoint} with the access_token, as the Messages page of the docs shows. Nothing is sent through the EasyCoexistence API.
6. Register my events URL with PUT /events-endpoint and verify X-EC-Signature on every event.
7. GET /channels lists the social channels the same way. Posts: POST /channels/{id}/posts with text, media and publish_at. Automations: POST /connections/{id}/automations or /channels/{id}/automations with a trigger and steps.
Ask me which number to use before you start, and stop to ask if any call returns an error.Reference
Every endpoint, by topic, in the menu. The same file as OpenAPI 3.1 and as text.