> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # Update a notification subscription > Update subscription endpoint to receive notifications. ## OpenAPI ````yaml openapi/configurations_2.yaml patch /v2/notifications/subscriptions/{id} openapi: 3.1.0 info: version: '1.0' title: API Overview description: Common endpoints shared across all W3S APIs. servers: - url: https://api.circle.com security: [] tags: - name: Health description: Inspect the health of the API. - name: Webhook Subscriptions description: Manage subscriptions to notifications. paths: /v2/notifications/subscriptions/{id}: patch: tags: - Webhook Subscriptions summary: Update a notification subscription description: | Update subscription endpoint to receive notifications. operationId: updateSubscription parameters: - $ref: '#/components/parameters/Id' - $ref: '#/components/parameters/XRequestId' requestBody: $ref: '#/components/requestBodies/UpdateSubscription' responses: '200': content: application/json: schema: $ref: '#/components/schemas/SubscriptionResponse' description: Successfully updated notification subscription. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' security: - BearerAuth: [] components: parameters: Id: name: id description: The universally unique identifier of the resource. in: path required: true schema: type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 XRequestId: name: X-Request-Id in: header description: > Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. **Must be a UUID to appear in logs.** Non-UUID values are accepted by the API but are ignored by logging and tracing systems. schema: $ref: '#/components/schemas/XRequestId' requestBodies: UpdateSubscription: content: application/json: schema: type: object required: - name - enabled properties: name: type: string description: Name of the subscription. example: Transactions Webhook enabled: type: boolean description: >- Whether the subscription is enabled. `true` indicates the subscription is active. example: true required: true description: Schema for the request payload to update a new subscription. schemas: SubscriptionResponse: title: SubscriptionResponse type: object properties: data: $ref: '#/components/schemas/Subscription' XRequestId: type: string format: uuid description: >- A unique identifier, which can be helpful for identifying a request when communicating with Circle support. example: 2adba88e-9d63-44bc-b975-9b6ae3440dde Subscription: type: object title: Subscription description: Contains information about a webhook notification subscription. required: - id - name - endpoint - enabled - createDate - updateDate properties: id: $ref: '#/components/schemas/Id' name: type: string description: Name of the webhook notification subscription. example: Transactions Webhook endpoint: type: string description: >- URL of the endpoint subscribing to notifications. Must be enabled to receive notifications. example: https://example.org/handler/for/notifications enabled: type: boolean description: >- Whether the subscription is enabled. `true` indicates the subscription is enabled. example: true createDate: $ref: '#/components/schemas/CreateDate' updateDate: $ref: '#/components/schemas/UpdateDate' notificationTypes: type: array description: The notification types on which a notification will be sent. items: $ref: '#/components/schemas/NotificationType' example: - '*' restricted: type: boolean description: >- Whether the webhook is restricted to specific notification types. An unrestricted webhook will notify on all notification types. A restricted webhook will only notify on the notification types in the `notificationTypes` field. example: false Id: type: string format: uuid description: System-generated unique identifier of the resource. example: c4d1da72-111e-4d52-bdbf-2e74a2d803d5 CreateDate: type: string format: date-time description: Date and time the resource was created, in ISO-8601 UTC format. example: '2023-01-01T12:04:05Z' UpdateDate: type: string format: date-time description: Date and time the resource was last updated, in ISO-8601 UTC format. example: '2023-01-01T12:04:05Z' NotificationType: type: string enum: - '*' - transactions.* - transactions.inbound - transactions.outbound - challenges.* - challenges.accelerateTransaction - challenges.cancelTransaction - challenges.changePin - challenges.contractExecution - challenges.createTransaction - challenges.createWallet - challenges.initialize - challenges.restorePin - challenges.setPin - challenges.setSecurityQuestions - contracts.* - contracts.eventLog - modularWallet.* - modularWallet.userOperation - modularWallet.inboundTransfer - modularWallet.outboundTransfer - travelRule.* - travelRule.statusUpdate - travelRule.deny - travelRule.approve - rampSession.* - rampSession.completed - rampSession.depositReceived - rampSession.expired - rampSession.failed - rampSession.kycApproved - rampSession.kycRejected - rampSession.kycSubmitted headers: XRequestId: description: > Developer-provided header parameter or Circle-generated universally unique identifier (UUID v4). Useful for identifying a specific request when communicating with Circle Support. schema: $ref: '#/components/schemas/XRequestId' responses: BadRequest: content: application/json: schema: type: object title: BadRequestResponse required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. example: code: 400 message: Bad request. description: Request cannot be processed due to a client error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' NotAuthorized: content: application/json: schema: type: object title: NotAuthorizedResponse required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. example: code: 401 message: Malformed authorization. description: >- Request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' NotFound: content: application/json: schema: type: object title: NotFoundResponse required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. example: code: 404 message: Not found. description: Specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: PREFIX:ID:SECRET description: >- Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are required to make a successful request. ````