The API Report CardAPI Index
Marchex

Marchex API

Conversation Intelligence / Call Tracking & Attribution · marchex.com

Marchex runs a public developer portal for its Marketing Edge v5 REST API covering numbers, call features, SMS logs, and reporting, with call lifecycle webhooks. Admins generate tokens self-serve in the Ordering Portal. AI fields like call summaries require separately licensed SKUs.

Last verified: July 2026Marketing & Sales
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA public developer portal documents the Marketing Edge v5 REST API, plus a separate Call Ad Network API.
AccessGOODEnterprise account admins generate organization tokens self-serve in the Ordering Portal.
CoverageMIXEDNumbers, call features, SMS logging, and reporting are covered; AI fields like call summaries need their paid SKUs licensed.
AuthMIXEDA non-standard dual-token scheme (organization token plus subscription key) instead of OAuth; thin guidance for non-admins.
Docs & DXMIXEDPortal docs plus an llms.txt machine index; no public sandbox, and webhook payload options vary by plan.
StabilityMIXEDRate limits are referenced in the docs but never published, making bulk export planning guesswork.
Supergood: Marchex has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Marchex scores C on the API Report Card. Marchex runs a public developer portal for its Marketing Edge v5 REST API covering numbers, call features, SMS logs, and reporting, with call lifecycle webhooks. Admins generate tokens self-serve in the Ordering Portal. AI fields like call summaries require separately licensed SKUs.

Tried to integrate with Marchex?
SOURCES
API access requires an enterprise account with admin role and is provisioned only through the Ordering Portal, no public sandbox or self-serve developer onboarding developer.marchex.io
Dual-token (x-organization-token + subscription-key) scheme is non-standard versus typical OAuth/bearer and is poorly documented for non-admin developers integrating downstream systems developer.marchex.io
Rate-limit thresholds are referenced in docs but specific limits are not published, making bulk export planning difficult developer.marchex.io
Conversation Intelligence outputs (Call Summary, scoring, signals, transcripts) require the corresponding paid SKUs to be licensed before they appear on the API, base call-tracking subscriptions cannot pull AI-derived fields marchex.com
Customers needing bulk programmatic access to recordings and transcripts report needing 'additional technical support' to set integrations up rather than self-serve g2.com
Webhook payload customization (Custom Call Webhooks) is a separate feature category and not all event types are available on every plan developer.marchex.io
Call Ad Network API requires emailing call-ad-network@marchex.com to obtain a publisher api_key, no self-serve credentialing call-ad-network-api.marchex.com
Pricing is opaque, no public pricing on the website, quote-only process makes it difficult for agencies to scope or upsell trustradius.com
Contract renegotiation to add services is reported as difficult and slow trustradius.com
Customer support responsiveness is hit-or-miss, with users reporting trouble getting timely technical assistance g2.com
In-product reporting is limited, users frequently have to export to spreadsheets to do meaningful analysis trustradius.com
UI is described as clunky and dated by a portion of reviewers, with onboarding flagged as cumbersome g2.com
Occasional 'Call DNA' analysis failures where calls are missing transcript/scoring data and the original recording cannot be re-analyzed g2.com
Integration setup often requires additional technical support engagement rather than self-serve configuration g2.com
Net losses every recent fiscal year (FY2024 net loss $4.9M; FY2025 net loss $5.2M; Q1 FY2026 net loss $1.7M) raise customer questions about long-term roadmap stability sec.gov