Skip to main content

API - Full event details

The callback URL receives event information including errors in its URL parameters. For some events you may require more details. You can use the API to obtain full details per each event.

For example, use the API to obtain the full list of translated files created. This action is notified by event type "CreatedTranslatedFiles".


To get a specific event in the project you are logged in:


To get a specific event in any project. You need to connect to the Beebox using the admin credentials:




The event id is included with push URLs and when enumerating all events. If the event does not exist an error message is returned.


The method returns full details of the event including the list of processed files. Example:

"id": 1002
"details": {



The resulting json is:



The unique id of the event.


Date of event.


Beebox project to which this event refers to.


Beebox project name.


User friendly description of the action.


A code identifying the type of event. This corresponds to the "bbid" parameter when using callbacks.


May contain additional information on the action. User friendly text.


The role of the initiator.


Boolean. True if the operation succeeded. False if it failed.


If the operation failed, this field contains a short error description.


Additional and event specific json details. For example the events of type "CreatedTranslatedFiles" and "SourceFileParsed" include the complete list of source or target files processed.

The property is always null if the API URL parameter

"fulldetails" is false.


If the Beebox project is configured to notify an external system of an event (push notification), then this is the URL that was called (or will be called).


Indicates the status of the push notification. Possible values are:

•  Waiting: The push was not yet done but will be within very shortly.

•  Skip: This event does not need to be pushed.

•  Done: Push done.

•  Failed: The URL could not be opened. If you see this kind of error please double check if the URL is valid and the Beebox server has the right to access the URL.


If administrator email notifications are enabled in the Beebox project of this event, then this property indicates whether the email is already sent out or not. Emails can be configured in the "Emailnotifications" tab of the project settings page.

The values are "Waiting" (email not yetsent), "Skip" (no email to send or emails disabled), "Done" (email sent) and "Failed" (email could not be sent).

Administrator emails are sent for all event types.

The "details" property has this structure:



Date when the file was processed. UTC and ISO formatted.


"S" if the operation refers to the analysis of a source file (text extraction).

"T" if the operation refers to the creation of the translated file.


If type is "S" then this is the source language. Otherwise it is a target language.


The full path of the source file


The full path of the translated file. Applies only if "type" is "T".


Optional text. Null if the operation succeeded. Otherwise a short error message.


Optional text. If the operation failed, this property contains verbose and technical error details.


When your URL is called it includes parameter "bbid" which is the related event ID. You can now connect to the API and retrieve the full event details. Please note that the login may occasionally time out due to running Beebox server operations. In fact automatic operations start immediately after the Beebox has opened the callback URLs. If you receive a timeout, please wait a few seconds and then try again.


See this page for an example:

Event Details - Created Translated Files

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.