> ## Documentation Index > Fetch the complete documentation index at: https://developers.zerion.io/llms.txt > Use this file to discover all available pages before exploring further. # Find subscriptions > List your webhook subscriptions, filtered by wallet or chain. ## OpenAPI ````yaml /openapi-v1.yaml get /v1/tx-subscriptions/ openapi: 3.0.3 info: version: 1.0.0 title: REST API description: REST-like API provides access to rich Zerion ecosystem. contact: name: Zerion API url: https://developers.zerion.io/ email: api@zerion.io servers: - description: Production API url: https://api.zerion.io security: - APIKeyBasicAuth: [] tags: - name: wallets description: >- Operations related to wallets, such as portfolio charts, positions, and transactions. - name: wallet sets description: >- Operations on a wallet set, returning aggregated portfolio data across at most one EVM address and one Solana address queried together. - name: fungibles description: >- Operations related to fungible assets, such as list them all, search or get by ID. - name: chains description: Operations related to chains, such as list all chains. - name: swap description: Operations related to swapping and bridging assets. - name: gas description: Operations related to gas. - name: nfts description: >- Operations related to non fungible assets, such list them, search or get by ID. - name: dapps description: >- Operations related to decentralized applications, such as list them all, search or get by ID. - name: subscriptions to transactions description: Operations related to subscriptions to transactions. paths: /v1/tx-subscriptions/: get: tags: - subscriptions to transactions summary: Find subscriptions description: > Returns your transaction subscriptions. The response is currently capped at 1000 subscriptions. **See also:** [Resource IDs](https://developers.zerion.io/endpoints-and-schema#resource-ids) operationId: findWalletTransactionsSubscription parameters: - name: filter[chain_ids] in: query required: false description: >- Return only subscriptions on these chains (comma-separated list). Only chains reporting both `supports_transactions` and `supports_positions` in the `flags` of `GET /v1/chains/` are accepted here. Naming a chain that fails that gate returns `400` rather than an empty result, with `detail` reading `chain does not support transactions`. That `detail` names the endpoint's capability rather than the flag that failed, so `bob` is refused with `chain bob does not support transactions` even though it reports `supports_transactions`. What it lacks is `supports_positions`. When the filter is omitted, the search covers every chain that passes the gate, and chains that fail it are left out silently, with no error and no `meta` signal. style: form explode: false schema: type: array items: type: string example: polygon responses: '200': $ref: '#/components/responses/SubscriptionsResponse' '400': $ref: '#/components/responses/MalformedParameters' '401': $ref: '#/components/responses/UnauthenticatedError' '429': $ref: '#/components/responses/TooManyRequests' components: responses: SubscriptionsResponse: description: Response for requested wallet's transactions subscription content: application/json: schema: $ref: '#/components/schemas/Response-21' MalformedParameters: description: Parameters are malformed content: application/json: schema: type: object properties: errors: type: array items: type: object properties: title: type: string description: Error short title example: Parameter is malformed detail: type: string description: Long description of the error example: Some validation errors will be described here UnauthenticatedError: description: Unathenticated request content: application/json: schema: type: object properties: errors: type: array items: type: object properties: title: type: string description: Error short title example: Unauthorized Error detail: type: string description: Long description of the error example: >- The API key is invalid, please, make sure that you are using a valid key TooManyRequests: description: Too many requests error content: application/json: schema: type: object properties: errors: type: array items: type: object properties: title: type: string description: Error short title example: Too many requests detail: type: string description: Long description of the error example: Your request had been throttled schemas: Response-21: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/Container-18' Container-18: type: object required: - type - id - attributes - relationships properties: type: type: string example: transactions_subscription id: type: string description: Unique ID of the transaction subscription. example: 52d994a173d755e99845e861d534a419 attributes: $ref: '#/components/schemas/Attributes-16' relationships: $ref: '#/components/schemas/Relationships-9' Attributes-16: type: object required: - callback_url - created_at - updated_at properties: callback_url: type: string description: Callback URL where updates delivered to example: https://webhook.site/fcd606d2-f5bd-4832-9874-ff07c980b5a3 created_at: type: string description: >- Timestamp string in ISO 8601 format when the subscription was created example: '2022-08-15T11:26:31+00:00' updated_at: type: string description: >- Timestamp string in ISO 8601 format when the subscription was last renewed example: '2022-08-15T11:26:31+00:00' filters: $ref: '#/components/schemas/Filters' Relationships-9: type: object properties: chains: type: array items: $ref: '#/components/schemas/Relationship' Filters: type: object nullable: true description: > Exclusion filters for the subscription. Conditions are combined with OR: an event matching any one of them is dropped and no webhook is delivered for it. Filters are absent from the response when none are set. What omitting the field or sending `null` means is specific to the request that carries it: see that operation's own description. Field paths below refer to the delivered webhook transaction payload, not to this subscription resource. A condition does not match an event lacking the value it compares, so an event with no `dapp` is not excluded by `protocol_ids`. required: - exclude properties: exclude: type: object description: Conditions that drop an event. At least one must be present. properties: types: type: array description: > Drop events by transaction type, matched against `attributes.operation_type`, not the resource-level `type` (always `"transactions"`), nor the per-act `acts[].type`. items: type: string example: send is_spam: type: boolean description: | Drop events classified as spam, delivered as `attributes.flags.is_trash`; there is no `is_spam` field in the payload. Only `true` is accepted. example: true protocol_ids: type: array description: > Drop events by protocol, matched against `relationships.dapp.id` only. items: type: string example: uniswap-v3 addresses: type: array description: > Drop events by address, matched against `attributes.sent_from` and `attributes.sent_to` only. items: type: string example: '0x0000000000000000000000000000000000000001' Relationship: type: object required: - links - data properties: links: $ref: '#/components/schemas/RelationshipLinks' data: $ref: '#/components/schemas/ContainerShort' RelationshipLinks: type: object required: - related properties: related: type: string format: url description: URL to the current chain. example: https://api.zerion.io/v1/chains/polygon ContainerShort: type: object required: - type - id properties: type: type: string description: Chain resource type. example: chains id: type: string description: Chain unique identifier. example: polygon securitySchemes: APIKeyBasicAuth: type: http scheme: basic description: >- To test endpoints here, paste your API key from the [Dashboard](https://dashboard.zerion.io/) into the username field and leave the password empty. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.