GET /webhooks/: List all configured webhooks.POST /webhooks/: Create a new webhook subscription.GET /webhooks/{id}/: Retrieve a specific webhook.PUT /webhooks/{id}/: Update a specific webhook.PATCH /webhooks/{id}/: Partially update a specific webhook.DELETE /webhooks/{id}/: Delete a webhook.POST /webhooks/{id}/regenerate-secret/: Invalidates the old secret and generates a new one for verifying payload signatures.POST /webhooks/{id}/test/: Sends a sample filing.processed.test event to the configured URL to help debug and validate the client's endpoint.POST /webhooks/ endpoint now enforces strict validation for the url field, including requiring HTTPS and performing DNS resolution to prevent SSRF (Server-Side Request Forgery) attacks against internal or reserved IP addresses.filing.processed event. This provides a clear data contract for the payload that will be sent to a user's endpoint, detailing the company and filing objects.type: ["string", "null"]) rather than the legacy nullable: true flag. This provides a more precise contract for data consumers.GET /filings/ endpoint now supports a new sources query parameter.?sources=38,40,51), allowing clients to efficiently query for filings from multiple sources in a single API call.GET /filings/ and GET /companies/ endpoints now support sorting by id (e.g., ?ordering=id or ?ordering=-id). This provides a consistent, incrementing key for more reliable pagination.ordering and source parameters on these endpoints has been updated to be more explicit and descriptive.id field.source, language, and filing_type objects returned by all endpoints (e.g., GET /filings/, GET /sources/) will now include their id.source object in a filing response will now appear as {"id": 38, "name": "Unternehmensregister", ...}.GET /sources/{id}/).on_watchlist query parameter to both the GET /filings/ and GET /companies/ list endpoints.?on_watchlist=true: Returns only items from companies on the user's watchlist.?on_watchlist=false: Returns only items from companies not on the user's watchlist.GET /companies/{id}/ and GET /companies/?view=full, has been updated to include additional data fields.description, description_last_updated, logoaddress, city, zip_codelocal_company_idshares_outstandingdesignated_sponsor, listed_stock_exchange, stock_indextagline field has been added to the Company object. This short, one-liner description is now available in both the summary and full views for the GET /companies/ and GET /companies/{id}/ endpoints, as well as in the nested company data within filing responses.GET /filings/ endpoint now supports a view=full query parameter. This allows clients to retrieve the complete filing object for each item in the list, providing more detail in a single request.updated_date_from and updated_date_to query parameters are now correctly implemented and documented for the GET /filings/ endpoint. This resolves a discrepancy from the 2025-08-12 changelog and enables proper data synchronization based on the last modified date.GET /companies/ endpoint now supports a view=full query parameter. This allows users to retrieve the complete company object for each item in the list, restoring access to detailed fields in response to user feedback.isins field on the Company object was not appearing in the API documentation for the /companies list and detail endpoints. This has been corrected, and the schema now accurately reflects that isins is an array of strings./filings/ and /companies/ now return a simplified "summary" response. This significantly reduces payload size and improves response times for list-based queries. The full object details remain available via the detail endpoints (e.g., /filings/{id}/).markdown_url field in the /filings/{id}/ response now links directly to a nested endpoint (/filings/{filing_id}/markdown/), logically connecting the content to its parent filing.GET /countries/: Returns a list of all supported countries and their ISO codes.GET /languages/: Returns a list of all supported filing languages.GET /filings/ endpoint to allow filtering by modification date, useful for data synchronization:updated_date_fromupdated_date_toGET /processed-filings/{id}/ endpoint has been removed in favor of the new nested markdown content endpoint for better API design and performance.