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
LaserData

LaserData Notification Channels API

Notification channels (email, slack, webhook)

Documentation Provider Profile APIs.io OpenAPI GitHub

LaserData Notification Channels API is one of 18 APIs that LaserData publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include NotificationChannels. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 12 operations across 6 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 0.0.66.

Requests are made against a single base URL, https://api.laserdata.cloud.

12 operations 6 paths 16 schemas 2 DELETE4 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.66
Base URL
https://api.laserdata.cloud
Authentication
API Key, API Key
Contact
LaserData Support
License
Proprietary
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

LaserData Notification Channels API declares 2 security schemes for authenticating requests. An API key is passed in the header as ld-api-key (ld_api_key). An API key is passed in the cookie as session (session_cookie). By default, every request must be authenticated.

  • ld_api_key — Tenant API key sent in the ld-api-key request header. Scoped to tenant-level audit reads. Cannot be used on user-scope endpoints (/audit/users/activity).
  • session_cookie — Browser session cookie issued by POST /account/signin on core. Required for user-scope endpoints.

Paths & Operations 12

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

Notification Channels 12

Notification channels (email, slack, webhook)

GET
/tenants/{tenant_id}/channels
List tenant notification channels
get_tenant_channels 4 params → 200403
POST
/tenants/{tenant_id}/channels
Create tenant notification channel
create_tenant_channel 1 param body → 201400403409
GET
/tenants/{tenant_id}/channels/{channel_id}
Get tenant notification channel
get_tenant_channel 2 params → 200403404
PUT
/tenants/{tenant_id}/channels/{channel_id}
Update tenant notification channel
update_tenant_channel 2 params body → 204400403404
DELETE
/tenants/{tenant_id}/channels/{channel_id}
Delete tenant notification channel
delete_tenant_channel 2 params → 204403404
POST
/tenants/{tenant_id}/channels/{channel_id}/test
Send test tenant notification
test_tenant_channel 2 params → 204400403404429
GET
/tenants/{tenant_id}/divisions/{division_id}/channels
List division notification channels
get_division_channels 5 params → 200403
POST
/tenants/{tenant_id}/divisions/{division_id}/channels
Create division notification channel
create_division_channel 2 params body → 201400403409
GET
/tenants/{tenant_id}/divisions/{division_id}/channels/{channel_id}
Get division notification channel
get_division_channel 3 params → 200403404
PUT
/tenants/{tenant_id}/divisions/{division_id}/channels/{channel_id}
Update division notification channel
update_division_channel 3 params body → 204400403404
DELETE
/tenants/{tenant_id}/divisions/{division_id}/channels/{channel_id}
Delete division notification channel
delete_division_channel 3 params → 204403404
POST
/tenants/{tenant_id}/divisions/{division_id}/channels/{channel_id}/test
Send test division notification
test_division_channel 3 params → 204400403404429

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are NotificationChannelInfo (8 properties), UpdateChannel (5 properties), CreateChannel (5 properties), Paged_NotificationChannelInfo (4 properties). Each schema is shown below with its type and property counts.

NotificationChannelDestination
string
NotificationChannelId
integer
NotificationChannelDetails
CreateChannel
object
5 properties 3 required
OwnerKind
string
NotificationChannelName
string
UpdateChannel
object
5 properties
WebhookSettings
object
2 properties
NotificationChannelKind
string
NotificationChannelInfo
object
8 properties 8 required
ChannelSettings
object
3 properties
SlackSettings
object
3 properties
SmsSettings
object
1 property
Paged_NotificationChannelInfo
object
4 properties 4 required
TenantId
integer
DivisionId
integer

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

laserdata-notification-channels-api-openapi.yml Raw ↑

Other APIs LaserData publishes across the network.

LaserData Account API
AE Profile APIs.io
LaserData API Keys API
AE Profile APIs.io
LaserData Audit API
AE Profile APIs.io
LaserData Billing API
AE Profile APIs.io
LaserData Cloud Accounts API
AE Profile APIs.io
LaserData Clouds API
AE Profile APIs.io
LaserData Connectors API
AE Profile APIs.io
LaserData Deployments API
AE Profile APIs.io
LaserData Divisions API
AE Profile APIs.io
LaserData Environments API
AE Profile APIs.io
LaserData Invitations API
AE Profile APIs.io
LaserData Members API
AE Profile APIs.io
#NotificationChannels
← Back to L APIs
API Details
ID
laserdata:laserdata-notification-channels-api
Base URL
https://api.laserdata.cloud
Docs
https://docs.laserdata.cloud/api
Provider
LaserData
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=laserdata-notification-channels-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/laserdata-notification-channels-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 LaserData Notification Channels 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.