Apideck Webhook Events API
The Webhook Events API from Apideck — 0 operation(s) for webhook events.
The Webhook Events API from Apideck — 0 operation(s) for webhook events.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/apideck-webhook-events-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Apideck Webhook Events API
version: 10.24.12
contact:
email: hello@apideck.com
url: https://developers.apideck.com
license:
name: Apache 2.0
url: http://www.apache.org/licenses/LICENSE-2.0.html
x-apideck-api: file-storage
x-apideck-sdk-support: true
x-logo:
url: https://developers.apideck.com/icon.png
description: 'Operations tagged Webhook Events across 2 of this provider''s published API definitions: apideck-file-storage-openapi.yml, apideck-webhook-events-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://unify.apideck.com
security:
- apiKey: []
tags:
- name: Webhook Events
paths: {}
webhooks:
FileCreated:
post:
summary: File Created
description: Event broadcast when a file has been created.
operationId: fileCreated
x-apideck-event-type: file-storage.file.created
parameters:
- name: x-apideck-event-type
in: header
required: true
description: The type of event that was triggered
schema:
$ref: '#/components/schemas/FileStorageEventType'
- name: x-apideck-signature
in: header
required: true
description: HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
schema:
type: string
example: 2c3b38f1a9b3349afe38829713dcd9722f47dec3ce8906ad93ce803a33f2a8a3
- name: x-apideck-idempotency-key
in: header
required: true
description: A unique identifier for the webhook event, can be used to prevent duplicate processing
schema:
type: string
example: e91dea5d-8ff6-4099-8b33-d3162fb4a042
tags:
- Webhook Events
requestBody:
content:
application/json:
schema:
type: object
properties:
payload:
$ref: '#/components/schemas/FileStorageWebhookEvent'
example:
payload:
event_type: file-storage.file.created
unified_api: file-storage
service_id: dropbox
consumer_id: test_user_id
event_id: d290f1ee-6c54-4b01-90e6-d701748f0851
entity_id: 123456ASDF
entity_url: https://unify.apideck.com/file-storage/files/123456ASDF
entity_type: file
occurred_at: '2020-01-01T00:00:00.000Z'
responses:
'200':
description: Return a 200 status to indicate that the data was received successfully.
security: []
servers:
- url: https://unify.apideck.com
FileUpdated:
post:
summary: File Updated
description: Event broadcast when a file has been updated.
operationId: fileUpdated
x-apideck-event-type: file-storage.file.updated
parameters:
- name: x-apideck-event-type
in: header
required: true
description: The type of event that was triggered
schema:
$ref: '#/components/schemas/FileStorageEventType'
- name: x-apideck-signature
in: header
required: true
description: HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
schema:
type: string
example: 2c3b38f1a9b3349afe38829713dcd9722f47dec3ce8906ad93ce803a33f2a8a3
- name: x-apideck-idempotency-key
in: header
required: true
description: A unique identifier for the webhook event, can be used to prevent duplicate processing
schema:
type: string
example: e91dea5d-8ff6-4099-8b33-d3162fb4a042
tags:
- Webhook Events
requestBody:
content:
application/json:
schema:
type: object
properties:
payload:
$ref: '#/components/schemas/FileStorageWebhookEvent'
example:
payload:
event_type: file-storage.file.updated
unified_api: file-storage
service_id: dropbox
consumer_id: test_user_id
event_id: d290f1ee-6c54-4b01-90e6-d701748f0851
entity_id: 123456ASDF
entity_url: https://unify.apideck.com/file-storage/files/123456ASDF
entity_type: file
occurred_at: '2020-01-01T00:00:00.000Z'
responses:
'200':
description: Return a 200 status to indicate that the data was received successfully.
security: []
servers:
- url: https://unify.apideck.com
FileDeleted:
post:
summary: File Deleted
description: Event broadcast when a file has been deleted.
operationId: fileDeleted
x-apideck-event-type: file-storage.file.deleted
parameters:
- name: x-apideck-event-type
in: header
required: true
description: The type of event that was triggered
schema:
$ref: '#/components/schemas/FileStorageEventType'
- name: x-apideck-signature
in: header
required: true
description: HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
schema:
type: string
example: 2c3b38f1a9b3349afe38829713dcd9722f47dec3ce8906ad93ce803a33f2a8a3
- name: x-apideck-idempotency-key
in: header
required: true
description: A unique identifier for the webhook event, can be used to prevent duplicate processing
schema:
type: string
example: e91dea5d-8ff6-4099-8b33-d3162fb4a042
tags:
- Webhook Events
requestBody:
content:
application/json:
schema:
type: object
properties:
payload:
$ref: '#/components/schemas/FileStorageWebhookEvent'
example:
payload:
event_type: file-storage.file.deleted
unified_api: file-storage
service_id: dropbox
consumer_id: test_user_id
event_id: d290f1ee-6c54-4b01-90e6-d701748f0851
entity_id: 123456ASDF
entity_url: https://unify.apideck.com/file-storage/files/123456ASDF
entity_type: file
occurred_at: '2020-01-01T00:00:00.000Z'
responses:
'200':
description: Return a 200 status to indicate that the data was received successfully.
security: []
servers:
- url: https://unify.apideck.com
DriveUpdated:
post:
summary: Drive Updated
description: Event broadcast when a drive has been updated.
operationId: driveUpdated
x-apideck-event-type: file-storage.drive.updated
parameters:
- name: x-apideck-event-type
in: header
required: true
description: The type of event that was triggered
schema:
$ref: '#/components/schemas/FileStorageEventType'
- name: x-apideck-signature
in: header
required: true
description: HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
schema:
type: string
example: 2c3b38f1a9b3349afe38829713dcd9722f47dec3ce8906ad93ce803a33f2a8a3
- name: x-apideck-idempotency-key
in: header
required: true
description: A unique identifier for the webhook event, can be used to prevent duplicate processing
schema:
type: string
example: e91dea5d-8ff6-4099-8b33-d3162fb4a042
tags:
- Webhook Events
requestBody:
content:
application/json:
schema:
type: object
properties:
payload:
$ref: '#/components/schemas/FileStorageWebhookEvent'
example:
payload:
event_type: file-storage.drive.updated
unified_api: file-storage
service_id: dropbox
consumer_id: test_user_id
event_id: d290f1ee-6c54-4b01-90e6-d701748f0851
entity_id: 123456ASDF
entity_url: https://unify.apideck.com/file-storage/drives/123456ASDF
entity_type: drive
occurred_at: '2020-01-01T00:00:00.000Z'
responses:
'200':
description: Return a 200 status to indicate that the data was received successfully.
security: []
servers:
- url: https://unify.apideck.com
components:
schemas:
FileStorageEventType:
x-apideck-enum-id: file-storage.event_type
type: string
enum:
- '*'
- file-storage.file.created
- file-storage.file.updated
- file-storage.file.deleted
- file-storage.drive.updated
example: file-storage.file.created
FileStorageWebhookEvent:
allOf:
- type: object
x-apideck-schema-id: WebhookEvent
properties:
event_id:
type: string
description: Unique reference to this request event
example: 9755c355-56c3-4a2f-a2da-86ff4411fccb
unified_api:
description: Name of Apideck Unified API
x-apideck-enum-id: unified_api
enum:
- accounting
- ats
- calendar
- crm
- csp
- customer-support
- ecommerce
- email
- email-marketing
- expense-management
- file-storage
- form
- hris
- lead
- payroll
- pos
- procurement
- project-management
- script
- sms
- spreadsheet
- team-messaging
- issue-tracking
- time-registration
- transactional-email
- vault
- data-warehouse
example: crm
type: string
service_id:
type: string
description: Service provider identifier
example: close
consumer_id:
type: string
example: test_consumer_id
description: Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
entity_id:
type: string
description: The service provider's ID of the entity that triggered this event
example: 123456ASDF
entity_type:
type: string
description: The type entity that triggered this event
example: Company
entity_url:
type: string
description: The url to retrieve entity detail.
example: https://unify.apideck.com/crm/contacts/123456
execution_attempt:
type: number
description: The current count this request event has been attempted
example: 2
occurred_at:
type: string
description: ISO Datetime for when the original event occurred
example: '2021-10-01T03:14:55.419Z'
- properties:
event_type:
$ref: '#/components/schemas/FileStorageEventType'
type: object
x-sdk-exclude: true
securitySchemes:
apiKey:
type: apiKey
in: header
name: Authorization
description: 'To access our API, you need to sign up and obtain your unique API key. Each Unify application is assigned a single API key. You can locate your API key in the Configuration Settings section of your Apideck application. Additionally, your application’s application_id is available on the same page.
Authenticate your API requests by including your test or live secret API key in the request header.
- Bearer authorization header: `Authorization: Bearer "YOUR_API_KEY_HERE"`
- Application id header: `x-apideck-app-id: "YOUR_APP_ID_HERE"`
You should use the public keys on the SDKs and the secret keys to authenticate API requests.
**Do not share or include your secret API keys on client side code.** Your API keys carry significant privileges. Please ensure to keep them 100% secure and be sure to not share your secret API keys in areas that are publicly accessible like GitHub.
Learn how to set the Authorization header inside Postman https://learning.postman.com/docs/postman/sending-api-requests/authorization/#api-key
Go to Unify to grab your API KEY https://app.apideck.com/unify/api-keys
'
externalDocs:
description: Apideck Developer Docs
url: https://developers.apideck.com
x-refined-from:
- apideck-file-storage-openapi.yml
# --- truncated at 32 KB (59 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/apideck/refs/heads/main/openapi/apideck-webhook-events-api-openapi.yml