> ## Documentation Index > Fetch the complete documentation index at: https://developers.portao3.com.br/llms.txt > Use this file to discover all available pages before exploring further. # List schedule events > Lists what happened to a schedule, newest first. The schedule's history: when it was created, changed or cancelled, each execution attempt and its outcome — with the error code of a failure and the IDs of what a successful run created — and when the customer was notified. Only an organization admin can read it. Filter by kind of event. Paginated — see [Pagination](https://developers.portao3.com.br/api-reference/pagination.md). ## OpenAPI ````yaml /api-reference/scheduling.openapi.json get /realms/{realmId}/organizations/{organizationId}/accounts/{accountId}/wallets/{walletId}/schedules/{scheduleId}/logs openapi: 3.0.3 info: title: Scheduling version: 1.0.0 description: >- Portão 3 scheduling API. Every endpoint requires a bearer token in the Authorization header (Authorization: Bearer ) unless its page states otherwise; see the Authentication guide. That requirement is not repeated per endpoint. Generated by tools/openapi from code (routes + security) and the hand-written spec (request/response bodies). Confidence tiers: generated:typed=7 copied:manual=0 unknown=0. servers: - url: https://api.scheduling.v2.portao3.com.br/ description: production - url: https://api.scheduling.dev.3pers.com.br/ description: development security: [] tags: - name: Schedules paths: /realms/{realmId}/organizations/{organizationId}/accounts/{accountId}/wallets/{walletId}/schedules/{scheduleId}/logs: get: tags: - Schedules summary: List schedule events description: Lists what happened to a schedule, newest first. operationId: >- getRealmsByRealmIdOrganizationsByOrganizationIdAccountsByAccountIdWalletsByWalletIdSchedulesByScheduleIdLogs parameters: - name: realmId in: path required: true description: |- ID of your realm. Format: `UUID` schema: type: string format: uuid example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b - name: organizationId in: path required: true description: |- ID of the organization the wallet belongs to. Format: `UUID` schema: type: string format: uuid example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 - name: accountId in: path required: true description: ID of the account (24 hexadecimal characters). schema: type: string pattern: ^[0-9a-fA-F]{24}$ example: 6702b1e4a9c3d80012f4a7b1 - name: walletId in: path required: true description: ID of the wallet the schedule pays from (24 hexadecimal characters). schema: type: string pattern: ^[0-9a-fA-F]{24}$ example: 6702b1e4a9c3d80012f4a7b5 - name: scheduleId in: path required: true description: |- ID of the schedule. Format: `UUID` schema: type: string format: uuid example: 3b9f7c2e-5d41-4e8a-9a6f-1c2d3e4f5a6b - name: events in: query required: false description: >- Only events of these kinds. --- Example (comma-separated list): `?events=EXECUTION_SUCCESS,EXECUTION_FAILED` schema: type: array items: type: string enum: - CREATED - EXECUTION_TRY - EXECUTION_FAILED - EXECUTION_SUCCESS - UPDATED - CANCELLED - NOTIFIED style: form explode: false - name: next in: query required: false description: >- Cursor returned as `next` by the previous page. Omit for the first page. schema: type: string example: 6719a0c4d8e1a30012b7c9fb - name: limit in: query required: false description: Page size. schema: default: 50 type: integer minimum: 1 maximum: 100 example: 50 responses: '200': description: Successful response content: application/json: schema: type: object properties: items: type: array items: type: object properties: id: type: string description: ID of the event. example: 8d2b6a4e-1f3c-4b5d-9e7f-0a1b2c3d4e5f format: uuid transactionSchedule: type: string description: ID of the schedule. example: 3b9f7c2e-5d41-4e8a-9a6f-1c2d3e4f5a6b format: uuid event: type: string enum: - CREATED - EXECUTION_TRY - EXECUTION_FAILED - EXECUTION_SUCCESS - UPDATED - CANCELLED - NOTIFIED description: >- What happened: created (`CREATED`), changed (`UPDATED`), cancelled (`CANCELLED`), an execution started (`EXECUTION_TRY`), succeeded (`EXECUTION_SUCCESS`) or failed (`EXECUTION_FAILED`), or the customer was notified (`NOTIFIED`). example: EXECUTION_SUCCESS failureCode: type: string description: Error code of a failed execution. example: INSUFFICIENT_FUNDS details: type: string description: Human-readable account of the event. example: Execution try initiated references: description: IDs of what a successful execution created. type: object properties: initiationId: type: string description: ID of the payment initiation (Pix or bank slip). example: 6719a0c4d8e1a30012b7c9f2 pixId: type: string description: ID of the Pix that paid the schedule. example: 6719a0c4d8e1a30012b7c9f2 bankSlipId: type: string description: >- ID of the bank slip payment that paid the schedule. example: 6719a0c4d8e1a30012b7c9f7 transferId: type: string description: >- ID of the transfer between wallets that paid the schedule. example: 6719a0c4d8e1a30012b7c9f9 nullable: true performedAt: type: string format: date-time description: When it happened. example: '2026-11-05T11:30:04.118Z' performedBy: type: string description: >- ID of the user who did it, or `system` for an automatic step. example: system required: - id - transactionSchedule - event - performedAt - performedBy description: Something that happened to a schedule. description: The events of this page. next: type: string nullable: true description: >- Cursor of the next page — send it as `next`. `null` on the last page. example: 6719a0c4d8e1a30012b7c9fb required: - items - next description: A page of a schedule's events, newest first. '403': description: >- `SCHEDULING_ADMIN_REQUIRED` — Only organization admins can read the schedules of a wallet. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - SCHEDULING_ADMIN_REQUIRED description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - SCHEDULING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: SCHEDULING_ADMIN_REQUIRED origin: SCHEDULING message: Organization admin required '404': description: >- `TRANSACTION_SCHEDULE_NOT_FOUND` — No schedule with this ID pays from this wallet. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - TRANSACTION_SCHEDULE_NOT_FOUND description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - SCHEDULING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: TRANSACTION_SCHEDULE_NOT_FOUND origin: SCHEDULING message: Transaction schedule not found '422': description: >- `BAD_REQUEST` — A path or query parameter is invalid; `fields` lists each one. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - BAD_REQUEST description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - SCHEDULING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. fields: type: array description: >- One entry per invalid request field (validation errors only). items: type: object properties: field: type: string description: >- Path of the invalid field, e.g. `label` or `values[0].value`. example: label message: type: string description: Why the field was rejected. example: label is required code: type: string description: >- `_` — e.g. `LABEL_REQUIRED`, `TYPE_ONE_OF`, `VALUES_VALUE_TYPE_ERROR`. example: LABEL_REQUIRED values: type: array items: type: string description: >- The accepted values, when the field is an enumeration. required: - field - message - code required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: BAD_REQUEST origin: SCHEDULING message: >- Bad Request: Your request is invalid or incomplete. Please make sure you are requesting with the right fields. fields: - field: limit message: 'Too big: expected number to be <=100' code: LIMIT_MAX ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.