AsyncAPI channel · EGYM
· EGYM MMS Webhook Events
/
The single registered callback URL receives every subscribed event type.
Channel address
/
Operations
receive
receiveMemberEvent
Receive an EGYM member event.
Messages
GYM_CHECKIN
A customer has physically checked in at a gym.
Content-Type:
application/jsonGYM_CHECKOUT
A customer has physically checked out from a gym.
Content-Type:
application/jsonEQUIPMENT_CHECKIN
A customer has physically logged in to equipment in a gym.
Content-Type:
application/jsonMEMBERSHIP_DELETE
Member data has been deleted from EGYM.
Content-Type:
application/jsonGENIUS_ONBOARDING_COMPLETED
A member completed EGYM Genius onboarding.
Content-Type:
application/jsonTEST
Verification event, fired on demand by POST /api/v2/webhooks/{id}/trigger.
Content-Type:
application/jsonAbout AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.