> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/integrations/events/types-of-sharinpix-events.md).
# Types of SharinPix Events
## What are SharinPix Events ?
SharinPix Events are particular events which are emitted when a specific action is performed on a SharinPix Album.
## Types of Events
### Client-side Events
**Client-side events** refers to SharinPix events emitted and used within an in-browser context.
| Event Name
| Trigger Action
|
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| image-new
| Triggered for each new image added to an album. |
| image-processed
| Triggered after upload when the exifs have been extracted from the uploaded image.
|
| upload-done
| Triggered when one or more images have already been added to an album. |
| image-deleted
| Triggered for each image deleted from an album. |
| tag-image-new
| Triggered for each new tag applied to an image. |
| tag-image-deleted
| Triggered for each tag removed from an image.
|
| viewer-image-viewed
| Triggered when the Large View mode is activated. |
| viewer-closed
| Triggered when the Large View mode is deactivated.
|
| images-selected
| Triggered for each image being selected. |
| image-annotated
| Triggered for each annotation created and applied to an image. |
| action
| Triggered whenever an action, which has been specified in the Apex Parameters, is executed. |
| restricted-file-error
| Triggered when uploading a restricted file type using the [upload\_accept parameter](https://docs.sharinpix.com/m/documentation/l/1649097-restrict-uploads-using-file-extensions). |
```javascript
// Capture in Javascript code
window.addEventListener('message', (event) => {
if (event.data.name == 'image-new') {
console.log(event.data.payload);
}
})
```
### Server-side Events
**Server-side events** refer to specific emitted events that either:
* execute predefined Apex methods or,
* make an HTTP POST request (**Webhook**) to predefined endpoints.
| Event name | Trigger Action |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New Image
| Triggered for each new image added to an album. |
| Processed image
| Triggered after upload when the exifs have been extracted from the uploaded image.
|
| New publication
| Triggered when a new Chatter Post is created through the SharinPix Chatter Component. |
| New tag image
| Triggered when a new tag is applied to an image. |
| Delete image
| Triggered when an image is deleted from an album. |
| Delete tag image
| Triggered when a Tag is deleted from an image. |
| Upload done
| Triggered once all images have been uploaded.
Note that if more than 50 images are uploaded at once, multiple events will be sent, each with at most 50 images.
|
| New Einstein prediction
| Triggered when a request for an Einstein prediction has been made and a response obtained in return. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sharinpix.com/documentation/integrations/events/types-of-sharinpix-events.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.