Post forms from plain HTML, run the whole booking flow over REST, and connect AI agents through the built-in MCP server.
{
"slots": [
{ "start": "2026-03-24T14:00" },
{ "start": "2026-03-24T15:00" }
]
}{
"id": "bk_a1b2c3d4",
"status": "confirmed"
}Point a form's action at your endpoint. Submissions arrive validated, screened for spam, and passed to your workflows.
No JavaScript, no server code
<!-- GoodInbound native form endpoint --> <form action="https://goodinbound.com/api/v1/forms/acme/contact" method="post"> <input name="full_name" /> <input name="email" /> <button>Send</button> </form>
Set the form's action to your GoodInbound endpoint and post. That is the whole integration.
Submit with one fetch call from React, Vue, or vanilla JS and keep your own markup and validation.
Every submission is screened for bots and can trigger emails, tags, and webhooks.
Send an email, a phone number, or a whole submission and get back facts plus a label your code can branch on.
POST /api/v1/leadscreen/checks
curl https://goodinbound.com/api/v1/leadscreen/checks \
-H "Authorization: Bearer $GOODINBOUND_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"fields": {"email": "jane@mailinator.com"}}'
{
"action": "screen_out",
"checks": {
"identity": { "result": "fail", "summary": "Disposable email" }
},
"email": {
"domain": "mailinator.com",
"valid": true,
"disposable": true,
"free": false,
"role": false,
"mx": null,
"work": false
}
}Disposable, free, role, and gibberish addresses, and whether the domain receives mail.
Valid for its country, fake patterns, line type, and the carrier for US and Canadian numbers.
Company, role, size, revenue, and LinkedIn for the contacts Lead Screen labels as leads.
Check open slots and create bookings over anonymous, rate-limited REST endpoints, then render the flow yourself.
Two requests, one confirmed meeting
# Check open slots
curl "https://goodinbound.com/api/v1/availability/acme\
?eventTypeSlug=intro-call&date=2026-07-01&timezone=UTC"
# Book one
curl -X POST https://goodinbound.com/api/v1/bookings \
-d '{ "projectSlug": "acme", "eventTypeSlug": "intro-call",
"name": "Sarah Chen", "email": "sarah@acme.com",
"startTime": "2026-07-01T14:00:00Z", "timezone": "UTC" }'Availability, booking, forms, and widgets work without an API key in the browser.
Skip the widgets and render booking and forms in your own frontend.
Use one project-scoped Bearer key for protected resources and keep it in secret storage.
Connect any MCP client to /api/mcp, sign in with OAuth, and choose a project. The agent never handles an API key.
Standard MCP client configuration
{
"goodinbound": {
"type": "http",
"url": "https://goodinbound.com/api/mcp"
}
}Bookings, availability, contacts, forms, workflows, analytics, and contact checks, read and write.
Bookings an agent creates send the same confirmations and trigger the same workflows.
Works with clients that support Streamable HTTP over MCP.
Every endpoint, widget, and MCP tool is documented in plain pages that people and coding assistants can both read.
One page per API area
One command connects Claude Code, Cursor, or any MCP client.
Each API area is a single page with every endpoint, parameter, and example.
Every endpoint comes with a working request you can run as it is.
Forms, booking pages, contacts, and workflows share one project, with GoodInbound Lead Screen built in.
Free screens every form for bots and fake sign-ups. Pro adds the message check that catches sales pitches, enrichment, and ad visit monitoring. Add-ons only raise limits.
Set your expected volume and the price updates as you go.
$0/month
Free, spam-filtered contact forms with notifications and workflows.
What you get:
Volume pricing, SSO and SCIM, security review, EU data residency, and a 99.9% uptime SLA.
No. Form submissions, widgets, availability, and booking creation use anonymous, rate-limited endpoints. Protected management endpoints use a project-scoped API key from your server.
Yes. Set the form's action to your GoodInbound endpoint and submit with a normal POST. No JavaScript or server code is needed.
Through the MCP server at /api/mcp. MCP clients connect over Streamable HTTP and sign in with OAuth in the browser, so the agent never handles an API key.
Yes. The checks endpoint validates emails and phone numbers in under 500 ms and returns the facts plus a pass, warn, or fail result.
REST API and MCP access are included on the free plan.