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
Events.com

Events.com Element Permissions API

Operations for managing element permissions

Documentation Provider Profile APIs.io OpenAPI GitHub

Events.com Element Permissions API is one of 113 APIs that Events.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Element Permissions. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 14 operations across 11 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://datagol-be.events.com.

14 operations 11 paths 12 schemas 2 DELETE8 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://datagol-be.events.com/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Events.com Element Permissions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (s_jwt).

  • s_jwt — Jwt Token

Paths & Operations 14

Across 11 paths, the API surfaces 14 operations — 2 DELETE, 8 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Element Permissions 14

Operations for managing element permissions

PUT
/noCo/api/v2/elementPermissions/{id}
Edit element permission
editElementPermissions 1 param body → 400403503500501200
DELETE
/noCo/api/v2/elementPermissions/{id}
Delete element permission
deleteElementPermission 1 param → 400403503500501200
GET
/noCo/api/v2/elementPermissions/link/{elementType}/{elementId}
Get link-level access for element
getLinkAccess 2 params → 400403503500501200
PUT
/noCo/api/v2/elementPermissions/link/{elementType}/{elementId}
Set link-level access for element
setLinkAccess 2 params body → 400403503500501200
POST
/noCo/api/v2/elementPermissions
Create element permission
createElementPermission body → 400403503500404501200
POST
/noCo/api/v2/elementPermissions/bulk
Bulk create element permissions
bulkCreateElementPermissions body → 400503403501500200
DELETE
/noCo/api/v2/elementPermissions/bulk
Bulk delete element permissions
bulkDeleteElementPermissions body → 400503403501500200
GET
/noCo/api/v2/elementPermissions/{elementType}
Get permissions by type
getPermissionsByType 3 params → 400503500403501200
GET
/noCo/api/v2/elementPermissions/{elementType}/{elementId}
Get element permissions
getElementPermissions 4 params → 400403503500501200
GET
/noCo/api/v2/elementPermissions/supported-types
Get supported element types
getSupportedElementTypes → 400503403501500200
GET
/noCo/api/v2/elementPermissions/matchedPermission/{elementType}/{elementId}
Get matched permission for user and element
getMatchedPermission 2 params → 400503403501500200
GET
/noCo/api/v2/elementPermissions/inviteInfo/{hash}
Get invite info by hash
getInviteInfoByHash 1 param → 400503500403501200
GET
/noCo/api/v2/elementPermissions/checkAccess/{elementType}/{elementId}
Check user access to element
checkUserAccess 2 params → 400503403501500200
GET
/noCo/api/v2/elementPermissions/checkAccess/{elementType}/{elementId}/{permission}
Check user access to element with required permission
checkUserAccessWithPermission 3 params → 400503403501500200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are UserDTO (21 properties), ElementPermissionsDTO (17 properties), InviteInfoDTO (6 properties), ErrorMessage (5 properties). Each schema is shown below with its type and property counts.

ElementPermissionsDTO
object
17 properties 2 required
EditElementPermissionsDTO
object
3 properties 1 required
UserDTO
object
21 properties
LinkAccessResponseDTO
object
2 properties
BulkOperationFailureDTO
object
3 properties
LinkAccessRequestDTO
object
2 properties 1 required
SaasxlResponseDTOObject
object
5 properties
BulkDeleteRequestDTO
object
1 property
ErrorMessage
object
5 properties
InviteInfoDTO
object
6 properties
BulkCreateRequestDTO
object
1 property
BulkOperationResponseDTO
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eventscom-element-permissions-api-openapi.yml Raw ↑

Other APIs Events.com publishes across the network.

DataGol MCP Server
AE Profile APIs.io
Events.com Agent Config Controller API
AE Profile APIs.io
Events.com Agent Config Migration Controller API
AE Profile APIs.io
Events.com Agent Email Controller API
AE Profile APIs.io
Events.com Agent Job Update Controller API
AE Profile APIs.io
Events.com Agent MCP API
AE Profile APIs.io
Events.com Agent MCP Config Controller API
AE Profile APIs.io
Events.com Agent Memory API
AE Profile APIs.io
Events.com Agent Skill Controller API
AE Profile APIs.io
Events.com Agent Template Controller API
AE Profile APIs.io
Events.com AI Feedback Controller API
AE Profile APIs.io
Events.com AI Third Party Page Controller API
AE Profile APIs.io
#Element Permissions
← Back to E APIs
API Details
ID
eventscom:eventscom-element-permissions-api
Base URL
https://datagol-be.events.com/
Docs
https://datagol-be.events.com/swagger-ui/index.html
Provider
Events.com
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=eventscom-element-permissions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/eventscom-element-permissions-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 Events.com Element Permissions 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.