An ads API where targeting the intimate is structurally impossible.
Drive your Echomi campaigns over REST: contextual targeting, editorial review, aggregated metrics. Personal data isn't filtered out — it simply isn't there.
API keys are issued to beta advertisers.
A sponsored question in the evening Drop.
Test mode · nothing is delivered
curl https://api.echomi.app/v1/campaigns \
-H "Authorization: Bearer echo_test_3c91…" \
-H "Content-Type: application/json" \
-d '{
"name": "Grain Coffee · Morning Drop",
"format": "question",
"billing": "cpe",
"budget": { "amount": 12000, "currency": "EUR" },
"schedule": { "start": "2026-07-01", "end": "2026-07-14" },
"targeting": {
"geo": ["FR", "BE"],
"min_age": 18,
"langs": ["fr"],
"interests": ["coffee", "food_drink"]
},
"creative": { "prompt": "Who deserves a coffee on you today?" }
}'{
"id": "cmp_8K2D",
"name": "Grain Coffee · Morning Drop",
"format": "question",
"billing": "cpe",
"status": "draft",
"budget": { "amount": 12000, "currency": "EUR", "spent": 0 },
"schedule": { "start": "2026-07-01", "end": "2026-07-14" },
"targeting": {
"geo": ["FR", "BE"],
"min_age": 18,
"langs": ["fr"],
"interests": ["coffee", "food_drink"]
},
"creative": { "prompt": "Who deserves a coffee on you today?" },
"editorial_review": { "state": "not_submitted" },
"created_at": "2026-06-08T10:24:00Z"
}- Base URL
- https://api.echomi.app/v1
- Authentication
- Authorization: Bearer echo_live_…
- Format
- REST · JSON · HTTPS
Four surfaces, nothing more.
Everything you need to launch, follow and measure a campaign. Nothing that touches people.
Campaigns
Create a Moment, Cosmetic or Question campaign, submit it for review, pause it, resume it.
- POST /campaigns
- PATCH /campaigns/{id}
- POST /campaigns/{id}/submit
Reporting
Aggregated metrics per campaign, per day or per format. Totals, never people.
- GET /campaigns/{id}/metrics
- GET /reporting
Webhooks
Get notified at every step: approved, rejected, active, paused, ended. Signed deliveries.
- POST /webhooks
- campaign.approved
Creatives
Questions, cosmetics and moment dressing, inside Echomi templates, reusable across campaigns.
- POST /creatives
- GET /formats
What the API can't do, even if you ask.
It's not a policy we promise to follow: these fields don't exist in the schema.
Never returns
- A member's name, number or identifier.
- Who picked whom, or what turned out mutual.
- The content of a conversation or a confession.
- Any individual answer: only totals.
Never accepts
- A list of people, phone numbers or emails to target.
- Targeting on picks, reveals or contacts.
- A minimum age under 18.
- Delivery inside a conversation or at reveal time.
Try to target a list of people: the request is refused before it reaches anything.
{
"error": {
"type": "invalid_request",
"code": "targeting_field_not_allowed",
"param": "targeting.custom_audience",
"message": "Targeting is contextual only: geo, min_age, langs, interests."
}
}Accepted: geo, min_age (≥ 18), langs, interests members chose themselves. Targeting in detail
From beta to your first campaign, in three steps.
- 1
Join the advertiser beta
Tell us who you are and what you want to build. The beta is private: we open access brand by brand.
Beta form - 2
Receive your keys
A test key (echo_test_…) to build with, a live key (echo_live_…) to deliver. Keep them server-side.
Authentication - 3
Run your first campaign in test mode
With the test key, create a campaign and submit it: the whole lifecycle runs, nothing is delivered in the app.
POST /campaigns
Once you have it, check your test key:
curl https://api.echomi.app/v1/me \
-H "Authorization: Bearer echo_test_3c91…"The response shows your advertiser account, your scopes and "key_env": "test".
Build ads nobody wants to block.
The first beta advertisers shape the API with us. Join them, and we'll come back to you with your keys.
A technical question before applying? sales@echomi.app