How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Mob.ly

Mob.ly Events API

The Events API from Mob.ly — 5 operation(s) for events.

Documentation Provider Profile APIs.io OpenAPI GitHub

Mob.ly Events API is one of 6 APIs that Mob.ly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 9 operations across 5 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version v0.

Requests are made against a single base URL, https://core-api.getmobly.com/api/v0.

9 operations 5 paths 15 schemas 2 DELETE4 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0
Base URL
https://core-api.getmobly.com/api/v0
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Mob.ly Events API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 9

Across 5 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Events 9
GET
/events
List events
2 params → 200400401403429500
POST
/events
Create event
body → 200400401
GET
/events/{eventId}
Get event
1 param → 200404
PUT
/events/{eventId}
Update event
1 param body → 200404
DELETE
/events/{eventId}
Delete event
1 param → 200404
GET
/events/{eventId}/leads
List event leads
3 params → 200
PUT
/events/{eventId}/leads
Add or update event leads
1 param body → 200
DELETE
/events/{eventId}/leads/{leadId}
Remove lead from event
2 params → 200
GET
/events/{eventId}/users
List event users
3 params → 200

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Event (9 properties), Location (8 properties), EventCreateV0Input (6 properties), EventUpdateV0Input (5 properties). Each schema is shown below with its type and property counts.

EventLeadV0Response
object
3 properties 3 required
UserV0Response
object
4 properties 4 required
EventUsersListResponse
object
3 properties 3 required
EventUpdateV0Input
object
5 properties 4 required
EventListResponse
object
3 properties 3 required
Location
object
8 properties
EventSingleResponse
object
2 properties 2 required
EventType
string
Event type classification.
EventLeadsListResponse
object
3 properties 3 required
EventAddLeadsV0Input
object
1 property 1 required
ErrorResponse
object
2 properties 2 required
EventLeadsUpdateResponse
object
2 properties 2 required
EventCreateV0Input
object
6 properties 5 required
Event
object
9 properties 6 required
Pagination
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mobly-events-api-openapi.yml Raw ↑

Other APIs Mob.ly publishes across the network.

Mob.ly Activations API
AE Profile APIs.io
Mob.ly Industry Events API
AE Profile APIs.io
Mob.ly Lead Activity Events API
AE Profile APIs.io
Mob.ly Leads API
AE Profile APIs.io
Mob.ly Tag Groups API
AE Profile APIs.io
#Event
← Back to M APIs
API Details
ID
mobly:mobly-events-api
Base URL
https://core-api.getmobly.com/api/v0
Docs
https://help.getmobly.com/api-reference
Provider
Mob.ly
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=mobly-events-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mobly-events-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Mob.ly Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.