Alfred v1.66.3.0
Alfred
Alfred
  • Introduction
  • Authentication
  • Event API
    • File Events
      • File Add To Job
      • File Category Create
      • File Category Delete
      • File Change Tag
      • File Done
      • File Extracted Data Create
      • File Extracted Data Delete
      • File Failed
      • File Move
      • File Move To Pending
      • File Move To Recycle Bin
      • File Property Create
      • File Property Delete
      • File Remove Tag
      • File Status Update
      • File Update
    • Job Events
      • JobCreateEvent
      • JobExceededRetriesEvent
      • JobFailedEvent
      • JobFinishedEvent
      • JobInvalidEvent
      • JobRetryEvent
      • JobStageUpdateEvent
      • JobStartEvent
    • Event Structures
  • endpoints
    • Alfred
    • File
      • Remote Sources
      • File Status
    • Deferred Session
    • Job
      • Job Stages
    • Tag
    • Metadata
    • Metadata Values
    • Report
    • Account
    • Company
Powered by GitBook
On this page
  • Event API
  • Job Events
  • File Events

Was this helpful?

  1. Event API

Event Structures

Event API

Event API distinguishes between two distinct event types that provide timely and relevant information of generated Jobs

Job Events

Job Events provide comprehensive details about jobs that are new, existing, or completed within the Alfred platform. These events can be retrieved regardless of whether they originated from a third-party application or were initiated directly within Alfred.

The JSON payload format for these events is as follows:

{
  "event_id": "A unique identifier for the event",
  "event_type": "The specific type of event that occurred",
  "event_time": "A Unix timestamp indicating when the event occurred",
  "event": {
    "description": "A detailed structure that varies based on the specific event."
  }
}

This structure ensures that users have access to consistent and essential information about each job event.

File Events

Job Events provide comprehensive details about specific files that belong to a job within the Alfred platform. These events can be retrieved regardless of whether they originated from a third-party application or were initiated directly within Alfred.

The JSON payload format for these events is as follows:

{
  "event_id": "A unique identifier for the event",
  "event_type": "The specific type of event that occurred",
  "event_time": "A Unix timestamp indicating when the event occurred",
  "event": {
    "description": "A detailed structure that varies based on the specific event."
  }
}

Last updated 1 year ago

Was this helpful?