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

IntegrationOS Event Access API

The Event Access API from IntegrationOS — 6 operation(s) for event access.

IntegrationOS Event Access API is one of 31 APIs that IntegrationOS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event Access. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, a getting-started guide, API documentation, and an engineering blog.

This API exposes 9 operations across 6 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 5.35.0.

Requests are made against the base URL https://api.withone.ai.

9 operations 6 paths 14 schemas 3 DELETE3 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.35.0
Base URL
https://api.withone.ai
Authentication
HTTP Bearer, OAuth 2.0, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 7

IntegrationOS Event Access API declares 7 security schemes for authenticating requests. It accepts HTTP bearer tokens (Bearer). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 38 scopes. An API key is passed in the cookie as withone (Session). An API key is passed in the header as X-One-Connection-Key (X-One-Connection-Key). An API key is passed in the header as X-One-Secret (X-One-Secret). An API key is passed in the header as X-One-Connection-Key (X-Pica-Connection-Key). An API key is passed in the header as X-One-Secret (X-Pica-Secret).

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 3 DELETE, 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Event Access 9
GET
/v1/event-access
List event access
list_event_access 2 params → 200400403404409500
POST
/v1/event-access
Create event access
create_event_access body → 200400403404409500
GET
/v1/event-access/organizations/{org_id}
--- Autometrics View the live metrics for the listorganizationkeys…
list_organization_event_access 4 params → 200400403404409500
POST
/v1/event-access/organizations/{org_id}
--- Autometrics View the live metrics for the createorganizationkey…
create_organization_event_access 2 params body → 200400403404409500
GET
/v1/event-access/organizations/{org_id}/projects/{project_id}
--- Autometrics View the live metrics for the listprojectkeys function…
list_project_event_access 5 params → 200400403404409500
POST
/v1/event-access/organizations/{org_id}/projects/{project_id}
--- Autometrics View the live metrics for the createprojectkey function…
create_project_event_access 3 params body → 200400403404409500
DELETE
/v1/event-access/organizations/{org_id}/projects/{project_id}/{key_id}
--- Autometrics View the live metrics for the deleteprojectkey function…
delete_project_event_access 4 params → 200400403404409500
DELETE
/v1/event-access/organizations/{org_id}/{key_id}
--- Autometrics View the live metrics for the deleteorganizationkey…
delete_organization_event_access 3 params → 200400403404409500
DELETE
/v1/event-access/{id}
Delete event access
delete_event_access 1 param → 200400403404409500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are OrganizationEventAccessView (18 properties), EventAccessView (18 properties), Params (8 properties), ErrorResponse (5 properties). Each schema is shown below with its type and property counts.

Paginated_OrganizationEventAccessView
object
4 properties 4 required
ConnectionType
string
OrganizationEventAccessView
object
Organization-scoped event access view for API keys
18 properties 14 required
ChangeLog
object
SecretKeyEnvironment
string
ConnectionDefinitionId
string
Prefixed ID with 'conndef' prefix (e.g., 'conndef1C'), also accepts raw integer
NonEmptyString
string
EventAccessView
object
18 properties 14 required
OrganizationEventAccessParams
object
5 properties 2 required
ErrorResponse
object
5 properties 5 required
Paginated_EventAccessView
object
4 properties 4 required
Page
object
3 properties
EventAccessId
string
Prefixed ID with 'evtac' prefix (e.g., 'evtac1C'), also accepts raw integer
Params
object
8 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

integration-os-event-access-api-openapi.yml Raw ↑

Other APIs IntegrationOS publishes across the network.

IntegrationOS Access API
IntegrationOS Actions API
IntegrationOS AI Agent Cron Runs API
IntegrationOS AI Agents API
IntegrationOS AI Runner Secrets API
IntegrationOS AI Runners API
IntegrationOS AI Skills API
IntegrationOS Auth Kit API
IntegrationOS Billing API
IntegrationOS Connection Definitions API
IntegrationOS Connection OAuth Definitions API
IntegrationOS Connections API
Where this information came from

This is an independent, third-party profile of IntegrationOS Event Access 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.