Meetin.gs API and webhooks

Short answer: Build custom scheduling flows and listen for lifecycle changes. Begin with “Create scoped credentials in a non-production environment.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Create scoped credentials in a non-production environment.Start with the intended outcome and the record that controls it.
Verify webhook signatures before parsing or storing payloads.Review every related setting before saving so one rule does not mask another.
Make consumers idempotent using event and delivery identifiers.Keep private data and guest-facing information clearly separated.
Exercise retry, delay, duplication, deletion, and version-change cases.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot Meetin.gs API and webhooks

These are the failures reported most often for this specific task, with the cause that explains each one.

The same webhook arrived twice.

At-least-once delivery is normal. Consumers must be idempotent on the event identifier — duplicate handling is your responsibility, not the sender's.

Signature verification fails.

Verify against the raw request body before any parsing or re-encoding. Middleware that reformats JSON is the usual cause.

A webhook stopped arriving.

Check whether your endpoint returned errors long enough to be disabled, then replay the missed window rather than assuming the gap is empty.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Meetin.gs API and webhooks acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Create scoped credentials in a non-production environment.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Verify webhook signatures before parsing or storing payloads.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Make consumers idempotent using event and delivery identifiers.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Exercise retry, delay, duplication, deletion, and version-change cases.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

CRM scheduling

Keep meeting activity, ownership, qualification, and follow-up aligned with your customer system. This page explains crm scheduling requirements. Confirm production availability before depending on this capability.

Review scope

Meetin.gs API and webhooks: frequently asked questions

Short answers to the questions organizers ask most about Meetin.gs API and webhooks.

Why did the same webhook arrive twice?

Delivery is at-least-once, so duplicates are normal and expected. Make consumers idempotent on the event identifier rather than assuming exactly-once delivery.

How do I verify a webhook is genuine?

Check the signature against the raw request body before parsing. Middleware that reformats JSON is the most common cause of verification failures.

What should an endpoint return?

A fast success status once the event is safely stored. Do the real work asynchronously — slow endpoints get retried and eventually disabled.

How should API credentials be managed?

Scope them narrowly, create them in a non-production environment first, store them outside source control, and name an owner for rotation.

NEXT PRODUCT STEPS

Related help and product guidance

Crm scheduling integration