Check any submission with one API call
Not on WordPress? Send each submission to Cayve’s API from your server and act on the answer: allow, hold or block, with reasons your team can read.
curl https://api.cayve.co/v1/check \
-H "Authorization: Bearer cv_live_…" \
-H "Content-Type: application/json" \
-d '{
"submission_id": "signup-81723",
"type": "signup",
"content": {
"name": "Dana Ruiz",
"email": "dana@example.com"
},
"submitter": { "ip": "203.0.113.9" }
}'
# The answer, usually in well under a second
{
"verdict": "allow",
"score": 4,
"category": "legit",
"reasons": [],
"mode": "enforce"
}What Cayve checks
- Any form, comment, review, sign-up or order
- Content, sender and network signals
- Page evidence, if you send it
When a message is held or blocked
You decide what each answer does in your app. Most teams deliver allowed messages, park held ones for review and drop blocked ones. If Cayve can’t be reached, let the submission through.
Best crypto signals here, guaranteed returns, join now at bit.ly/…
Why
- It promotes cryptocurrency or trading (crypto signals, guaranteed returns).
- It uses a link shortener, which hides where the link really goes.
- The same message was sent to 31 other websites in the last day.
- This form normally sends Cayve's security token, but this message didn't. It was most likely sent straight to your server by a program.
Set it up
Create an account and add a site in the Cayve dashboard.
Create a key (test keys give fixed answers and aren’t counted).
POST each submission to /v1/check from your server.
Send /v1/feedback when your team marks something, so Cayve learns.
Keys stay on your server; never call the API from the browser.
The same submission id sent twice is answered once and counted once.
Get a test key in a minute.
Test keys give fixed answers and are never counted, so you can build and test before you go live.