Contact Form 7 to API
by Kenny Meyer · Forms
Send Contact Form 7 submissions to a remote API with GET or POST.
Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.
Health
B 84/100
Few reviews
Active installs
1K+
≈1.6K estimated
Momentum
+28%
downloads vs prior 30d
Biggest opportunity: Swap “contact form 7” for “wpcf7”. “contact form 7” isn't earning its slot: you're not in the first 24 results for its own search. “wpcf7” sits at #16 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
84 health vs 65 average across 2,510 Forms plugins
Install conversion
How it's measured →3.2%
of downloads still active
At least 1K of 31.2K lifetime downloads are still running, above its category: the median Forms plugin keeps 1.3%, across 1,667 plugins.
Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Forms plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.
This plugin shipped 5 releases in the last 12 months, and every existing install that updated counted as another download. wp.org publishes no split between first installs and updates, so we show the raw rate rather than guess at one.
Details
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Excellent listing optimization
Most to gain: Rating quality
Updated 18 days ago
Tested up to WordPress 7.1.4, the current branch or newer
4.3★ over 6 reviews, smoothed to 4.12★ and held back under 25 reviews
5 of 5 tags set · short description in place
To rank higher: Too few reviews to rank on quality — nudge happy users to leave one.
Get the full rank-higher report →Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
40
Momentum
Mixed: one swing, the rest drifting
0.0
Velocity
places per keyword, 19d
22%
Breadth
of keywords climbing, 19d
+0.0
Acceleration
recent half vs earlier
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| remote api | #3 | #12 | up 1 |
| api your tag | #24 | #22 | 0 |
| wpcf7 | #16 | #10 | 0 |
| remove rest api | #13 | #20 | 0 |
| ip api | #22 | #20 | up 1 |
| json rest api | #24 | #20 | — |
| contact form 7 your tag | Not in the top 24 | ||
| crm your tag | Not in the top 24 | ||
| rest api your tag | Not in the top 24 | ||
| webhook your tag | Not in the top 24 | ||
29 searches this plugin appeared in over the last 90 days, 6 listed. 23 left out as unrelated or noise (years, numbers, stray words). 4 of its tags aren't in the top 24 for their own search.
What to do about it
- Swap “contact form 7” for “wpcf7”. “contact form 7” isn't earning its slot: you're not in the first 24 results for its own search. “wpcf7” sits at #16 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
Daily downloads
Since 5 Oct 2022 · 1,488 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 1.6K · peaks are release surges
Directory rank vs rivals
wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you
Rating trend
Star average over time · dips mark rough releases
Health trend
Composite health score, snapshotted daily
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
Actively maintainedHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
5
releases in the last 12 months
18d ago
latest release · v1.5.4 · 13 Oct 2026
15
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “1K+”. Our estimate pins where the real number sits.
Crossed into this band 7 months ago; the previous band took 18 months to cross, which places it about 59% of the way through.
Install history since 27 Jul 2021
Recent reviews
All reviews on wp.org ↗- ★★★★★ utkarshs4.9y ago
Plugin is Dead…doesn’t save settings anymore This topic was modified 4 years, 7 months ago by utkarshs.
Read on wp.org ↗ - ★★★★★ hotelwww4.9y ago
Did not work to save data in version 5.8.2
Read on wp.org ↗ - ★★★★★ hausi915.3y ago
does what I expected it to do. so five stars from me!
Read on wp.org ↗ - ★★★★★ Host Domination5.6y ago
great plugin!!! one of a kind, simple and easy to set up.
Read on wp.org ↗ - ★★★★★ dasherg6.3y ago
Extremely useful and easy to use.
Read on wp.org ↗ - ★★★★★ George Pattichis6.6y ago
Does exactly what it says with no problems. Thank you very much!
Read on wp.org ↗
Behavioral tests
via WP HiveAutomated install-time checks, tested on PHP 7.4.8 · WP 5.8
AI assistants
How it's measured →Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.
Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.
Readme readiness
6 of 8 pass · checked 29 Oct 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ✓ Says what it does "Send Contact Form 7 submissions to a remote API with GET or POST."
- ✓ Has a FAQ 9 questions in the FAQ.
- ✓ FAQ asks real questions 9 of 9 read like questions a user would type.
- ! Names who it is for Never says who the plugin is for or what they use it for.
- ✓ Names what it works with Mentions Contact Form 7.
- ✓ Headings and lists 4 headings and 3 lists.
- ✓ Enough to quote 3,209 characters of description.
- ! Tags match the text Only 2 of 5 tags appear in the text ("crm", "rest-api", "webhook" missing).
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2026-03-25 2K+ → 1K+ down after 543 days in tier
- 2024-09-28 3K+ → 2K+ down after 1 days in tier
- 2024-09-27 2K+ → 3K+ up after 2 days in tier
- 2024-09-25 3K+ → 2K+ down after 445 days in tier
- 2023-07-08 4K+ → 3K+ down after 360 days in tier
- 2022-07-13 3K+ → 4K+ up
Competes with
The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).
-
Contact Form to Any API 8K+ installs · 4.7★ · 4 shared tags A -
Redirection for Contact Form 7 200K+ installs · 4.7★ · 2 shared tags A -
Disable REST API 80K+ installs · 4.6★ · 2 shared tags D -
Make Connector 70K+ installs · 3.1★ · 2 shared tags B -
Disable WP REST API 30K+ installs · 4.6★ · 2 shared tags A -
WordPress REST API (Version 2) 10K+ installs · 4.1★ · 2 shared tags D
Embed this report card
Drop a live Pulse card for Contact Form 7 to API into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/cf7-to-api-basic-auth" width="480" height="300" style="border:0" loading="lazy" title="Contact Form 7 to API — Plugin Pulse"></iframe> Contact Form 7 to API: 1K+ active installs, 4.3★ (6 reviews). Plugin Pulse (WP Mayor), as of 2026-10-31. https://plugins.wpmayor.com/plugin/cf7-to-api-basic-auth
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.