> ## Documentation Index > Fetch the complete documentation index at: https://docs.pingintel.com/llms.txt > Use this file to discover all available pages before exploring further. # List Submission Events > List submission events since a `start` time or since the last `cursor_id`, in ascending time order, filtered by team, division, or pingid. Intended primarily for system-to-system periodic polling to stay up-to-date with all events, to keep systems in sync. Events include status changes (event_type=SSC), various job stages like Results Received (SFRR), etc. One or more of `division_id`, `team_id`, or `pingid` must be provided. ## OpenAPI ````yaml https://vision.staging.pingintel.com/api/schema/?format=json get /api/v1/submission-events openapi: 3.0.3 info: title: Ping.Vision API version: v1.0 description: > ### Ping.Vision API This API provides convenient, efficient access to Ping Intel's data and services. It is designed to be used by developers and data scientists to integrate Ping Intel's capabilities into their applications. Once SSO is set up with your organization, you can create an Organization or Personal API key at https://auth.pingintel.com/org. Please see the Python client library [pingintel-api](https://pypi.org/project/pingintel-api/) for commandline tools and programmatic access, and you can refer to the following documentation for details on interacting with the system via the HTTP API. contact: email: support@pingintel.com name: Ping Intel url: https://www.pingintel.com servers: - url: https://vision.pingintel.com description: Ping.Vision API - url: https://vision.staging.pingintel.com description: Ping.Vision API (staging) security: [] tags: - name: Create Submission description: The Create Submission API allows you to add new data into the system. - name: Update Submission description: >- The Update Submission API provides various endpoints to update, modify, or act upon existing submissions. - name: Get Submission Data description: '' - name: User Memberships description: >- The User Memberships API allows you to add, remove, and change the role of users in different teams, divisions, or companies. - name: Miscellaneous description: '' paths: /api/v1/submission-events: get: tags: - Get Submission Data summary: List Submission Events description: >- List submission events since a `start` time or since the last `cursor_id`, in ascending time order, filtered by team, division, or pingid. Intended primarily for system-to-system periodic polling to stay up-to-date with all events, to keep systems in sync. Events include status changes (event_type=SSC), various job stages like Results Received (SFRR), etc. One or more of `division_id`, `team_id`, or `pingid` must be provided. operationId: api_v1_submission_events_retrieve parameters: - in: query name: cursor_id schema: type: string format: uuid nullable: true description: >- Optional. If iterating through a result set, this is the cursor ID to start from, obtained from the last response's cursor_id field. - in: query name: division schema: type: string minLength: 1 description: >- Optional. The division UUID to filter results by. (Must include at least one of division, team, or pingid.) - in: query name: page_size schema: type: integer maximum: 250 minimum: 1 default: 50 description: Optional. The maximum number of results returned in a page. - in: query name: pingid schema: type: string minLength: 1 description: >- Optional. The pingid to filter results by. (Must include at least one of division, team, or pingid.) - in: query name: start schema: type: string format: date-time nullable: true description: >- Optional. Start timestamp for which results will be returned. All timestamps are UTC. It should be formatted like `%Y%m%d%H%M%S`. E.g. `Jan 1 2023 1:00 PM` would be given as `20230101130000`. - in: query name: team schema: type: string minLength: 1 description: >- Optional. The team UUID to filter results by. (Must include at least one of division, team, or pingid.) responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListSubmissionEventsResponse' description: '' security: - authorization_header: [] components: schemas: ListSubmissionEventsResponse: type: object properties: cursor_id: type: string format: uuid nullable: true description: >- Provide this cursor_id back to the API to get the next page of results. results: type: array items: $ref: '#/components/schemas/ListSubmissionEventResponse' description: List of submission events. required: - cursor_id - results ListSubmissionEventResponse: type: object properties: created_time: type: string format: date-time description: The timestamp of when the event occurred. division_uuid: type: string format: uuid description: The team UUID of the event. event_type: enum: - NEW - SSC - UC - SN - CBC - SFI - SFRR - SFF - SFUR - ERR - SCC - ROUT - OC - OEM - DU type: string x-spec-enum-id: c24a697d3faf019a description: |- The type of event. * `NEW` - NEW_SUBMISSION * `SSC` - SUBMISSION_STATUS_CHANGE * `UC` - USER_COMMENT * `SN` - SYSTEM_NOTE * `CBC` - CLAIMED_BY_CHANGE * `SFI` - SOV_FIXER_INVOKED * `SFRR` - SOV_FIXER_RESULTS_RECEIVED * `SFF` - SOV_FIXER_FAILED * `SFUR` - SOV_FIXER_UPDATE_RECEIVED * `ERR` - ERROR * `SCC` - SCRUBBING_COMPLETE * `ROUT` - RUN_OUTPUTTERS * `OC` - OUTPUTTERS_COMPLETE * `OEM` - OUTPUTTERS_EMAILED * `DU` - DOCUMENT_UPLOADED message: type: string description: The message associated with the event. pingid: type: string description: The pingid associated with the event. uuid: type: string format: uuid description: The unique identifier for the event. metadata: nullable: true description: >- Additional metadata associated with the event, such as job_id, outputs, etc. new_value: type: string nullable: true description: >- The new value associated with the event. For event_type SSC, this is the new status ID. old_value: type: string nullable: true description: >- The old value associated with the event. For event_type SSC, this is the old status ID. user_id: type: integer nullable: true description: The user ID associated with the event. required: - created_time - division_uuid - event_type - message - pingid - uuid securitySchemes: authorization_header: type: apiKey in: header name: Authorization description: >- Supports `Token `-prefixed API keys and `Bearer `-prefixed JWT-based authentication. ````