\"specType\": \"SPEC_TYPE_OPEN_API_SPEC\",\n \"configKey\": \"file_0\",\n \"apiNamingEnabled\": true,\n \"apiDiscoveryEnabledV2\": true,\n \"postUploadOperations\": [{ \"apiDiscoveryData\": { \"apiDiscoveryEnabled\": true,\n \"openApiSpec\": {},\n \"apiAttribute\": { \"environmentConfig\": { \"values\": { \"values\": [ \"your_env\" ] } } },\n \"apiDiscoveryScope\": { \"discoverAll\": {} } } }] } }] }"' \ --form 'file_0=@"/path/to/your

the grouped attribute. This is helpful as it provides teams with a way to prioritize threats based on the count, focusing on higher activity counts that may require immediate attention. IP Count — Displays the total number of IPs Traceable observed

called SSL_read and SSL_write functions, which can lead to high CPU overhead for some processes like Ruby, the tracer can now place probes on the TLS handshake function. This ensures uprobes are executed only once per new TLS

function application, navigate to Settings → Configuration to add the environment variable and save the configuration. Environment variable Description TA_SERVICE_NAME (Optional) The name with which you would like to identify the service in Traceable Platform. The default service name

Local File Inclusion Mass Assignment Missing Field NodeJS Injection Rate Limiting Region Malicious Sources Remote Code Execution Remote File Inclusion Scanner Detection Server Side Request Forgery (SSRF) Signatures Session Fixation SQL Injection Type Anomaly Value Out of Range XML

descriptions. Field Type Description eventType String Identifies the event as DOMAIN_DISCOVERY . domainName String Fully qualified domain name (FQDN) of the newly discovered domain observed in API traffic. 3. Environment entity change notification type The following table outlines the fields

naming rules should be generated "apiDiscoveryEnabledV2": false //Whether or not API discovery should run after upload } } ] } Sample Response [ { "docId": "ec262335-643d-4539-870f-02c418993c96", "jobIds": [], "messages": [], "uploadStatus": "PARSING_SUCCESSFUL" } ] Update API Documentation You can use this operation to modify the

New Rule Click + Rules and select Blank Rule Template . Provide a rule name, such as Invoke Traceable EdgeWorker . Define Criteria for Invoking EdgeWorker Criteria : Set Path to Matches one of and add /* to capture all traffic. Optionally, to narrow the

Traceable stores a query for three days, after which it is deleted. If you wish to retain these queries, you can save them according to your requirements. Time Range — The time range that you selected in the Explorer tab while

Updates (October 2025 to December 2025) October 2025 — Updated the page to add information about issues detected in scans created using AI Scan Policies (Beta). The Issues page serves as your central command center for monitoring API risks that Traceable

process sensitive data, such as Personally Identifiable Information (PII), Social Security Numbers (SSN), or authentication tokens. This helps you identify risks associated with data privacy. For more information, see Sensitive Data . Posture Events — Provides information on discovery-related changes in

{"template":{"metadata":{"annotations":{"mirror.traceable.ai/mode":"egress"}}}} }' Namespace To capture egress traffic at the namespace level, set the annotation mirror.traceable.ai/defaultMode  to egress . Enter the following: kubectl annotate namespace mirror.traceable.ai/defaultMode=egress Capture ingress

according to your requirements. Create Attribute Delete — Delete the custom entity. Note A deleted entity cannot be restored. After creating custom entities, you can use them in Bot Protection policies to build more granular aggregation logic, improve detection accuracy, and

0.1.93 — 10 th April Traceable’s NGINX agent 0.1.93 provides the following: Resolved issue Amazon Linux RPM Support: Fixed an issue that prevented the NGINX module from installing on Amazon Linux due to overly strict RPM

in result.text: raise Exception("Authentication failed with token %s and cookies %s" % (token, cookies), result.text) cookies = result.cookies.get_dict() cookies = {k: v for k, v in cookies.items() if k.startswith("_")} return cookies def api_key_hook

PolicyBinding.spec.targetRef.namespace . apiVersion: gateway.mulesoft.com/v1alpha1 kind: PolicyBinding metadata: name: traceable-https-egress-service-binding spec: targetRef: kind: Service name: traceable-https-egress-service namespace: default policyRef: name: tls-outbound config: skipValidation: true trustedCA: | # -----BEGIN CERTIFICATE----- # insert

You can configure TLS communication between Traceable's Apigee agent and Traceable's Platform agent. Make a note of the following points before you begin:  Make sure that Traceable Platform agent's TLS is already set up. Configure the following

Netlify is a deployment platform for modern web applications. It provides a global content delivery network, builds automation, serverless functions, and Edge Functions. Edge Functions allow you to run JavaScript at the edge of the Netlify network. They can intercept

Updates (April 2026 to June 2026) June 2026 — Updated the topic to add information about the steps to create an API naming exclusion rule according to the latest Traceable user interface. For more information, see Setting up API Discovery , API

This guide outlines the steps to deploy the Traceable Agent on Fastly as a Compute@Edge service. Fastly is a robust content delivery network (CDN) and edge cloud platform that provides fast, secure, and scalable application delivery. Integrating Traceable with