Deploy Hooks

One URL that automatically submits a human QA test every time you deploy. No API key needed in your CI — just POST to the URL.

What is a Deploy Hook?

A deploy hook is a unique URL assigned to each project. When you send a POST request to it, TestMyVibes automatically:

Creates a QA test using your project's saved settings (URL, test type, SLA)
Deducts credits from your account
Includes regression checks from previous test failures
Sends results to your webhook URL if configured

Getting Your Hook URL

Every project gets a deploy hook automatically when created. Find it on your Projects page — it's shown at the bottom of each project card.

Your deploy hook URL looks like:

https://testmyvibes.com/hooks/deploy/YOUR_UNIQUE_TOKEN

Treat this URL like a secret. Anyone with it can trigger tests (and spend your credits). Don't commit it to public repos — use environment variables.

Usage

Just send a POST request with no body required:

curl -X POST https://testmyvibes.com/hooks/deploy/YOUR_TOKEN

You can optionally pass a JSON body to override settings:

curl -X POST https://testmyvibes.com/hooks/deploy/YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://staging.myapp.com",
    "title": "Staging deploy #42"
  }'

Response

{
  "success": true,
  "jobId": "abc123",
  "message": "Test submitted via deploy hook",
  "credits": {
    "deducted": 3,
    "remaining": 47
  }
}

Error Responses

Status	Meaning
`404`	Invalid or expired deploy hook token
`400`	Project has no URL configured
`402`	Insufficient credits — buy more at your billing page

Smart Regression Testing

Deploy hooks are smarter than regular test submissions. They automatically:

Pull in failures from the last test — if your previous test found that "About page returns 404", the next deploy hook test will include that as a regression check item
Consume prepared regressions — if you've added manual regression items to your project, they'll be included in the next deploy hook test
Build smarter checklists — the AI checklist generator receives context about previous failures to create more targeted tests

Platform Examples

Replit

Store the hook token as a Replit Secret, then call it from your post-deploy script:

curl -X POST https://testmyvibes.com/hooks/deploy/$TMV_DEPLOY_TOKEN

Tip: Add TMV_DEPLOY_TOKEN as a Secret in your Replit project's Secrets tab so it's never exposed in code.

Vercel

Add as an outgoing webhook in Vercel project settings under Deploy Notifications.

Netlify

Add as a deploy notification webhook (Event: "Deploy succeeded").

GitHub Actions

- name: Trigger QA Test
  run: curl -s -X POST https://testmyvibes.com/hooks/deploy/${{ secrets.TMV_DEPLOY_TOKEN }}

Railway

# After railway up:
railway up && curl -X POST https://testmyvibes.com/hooks/deploy/$TMV_DEPLOY_TOKEN

Render

Add the deploy hook URL as a webhook notification in your Render dashboard under Settings → Notifications.

Fly.io

# After fly deploy:
fly deploy && curl -X POST https://testmyvibes.com/hooks/deploy/$TMV_DEPLOY_TOKEN

Lovable

After deploying your Lovable app, trigger a QA test with the deploy hook:

curl -X POST https://testmyvibes.com/hooks/deploy/$TMV_DEPLOY_TOKEN

Docker / Custom CI

#!/bin/bash
# deploy.sh
docker build -t myapp .
docker push myapp:latest
kubectl apply -f deployment.yaml

# Trigger QA test
curl -X POST https://testmyvibes.com/hooks/deploy/$TMV_DEPLOY_TOKEN

Combining with Webhooks

Deploy hooks work great with webhooks. Set up a webhook URL on your project, and the flow becomes fully automated:

You deploy → deploy hook fires → test is created
A human tester checks your app
Test completes → webhook delivers results to your server
Your server processes results (create tickets, send alerts, update dashboards)