You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
--- a/schemas/fingerprint-server-api-v4-normalized.yaml+++ b/schemas/fingerprint-server-api-v4-normalized.yaml@@ -413,18 +413,28 @@
will match events with a Bot Info Name of `ChatGPT Agent` or
`Bedrock AgentCore`. Other notations like comma-separated or bracket
notation are not supported.
- name: ip_address
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by IP address or IP range (if CIDR notation is used).
If CIDR notation is not used, a /32 for IPv4 or /128 for IPv6 is
assumed.
Examples of range based queries: 10.0.0.0/24, 192.168.0.1/32
+++ Multiple IP addresses can be provided using the repeated keys+ syntax. For example,+ `ip_address=192.168.0.1&ip_address=10.0.0.0/24`, will match events+ with either IP address or range. Other notations like+ comma-separated or bracket notation are not supported.
- name: asn
in: query
schema:
type: string
description: >
@@ -432,22 +442,32 @@
This corresponds to the `ip_info.(v4|v6).asn` property in the
response.
- name: linked_id
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by your custom identifier.
You can use [linked
Ids](https://docs.fingerprint.com/reference/js-agent-v4-get-function#linkedid)
to associate identification requests with your own identifier, for
example, session Id, purchase Id, or transaction Id. You can then
use this `linked_id` parameter to retrieve all events associated
with your custom identifier.
+++ Multiple linked Ids can be provided using the repeated keys syntax.+ For example, `linked_id=session-1&linked_id=session-2`, will match+ events with a linked Id of `session-1` or `session-2`. Other+ notations like comma-separated or bracket notation are not+ supported.
- name: url
in: query
schema:
type: string
description: |
--- a/schemas/fingerprint-server-api-v4-with-examples.yaml+++ b/schemas/fingerprint-server-api-v4-with-examples.yaml@@ -1514,18 +1514,28 @@
will match events with a Bot Info Name of `ChatGPT Agent` or
`Bedrock AgentCore`. Other notations like comma-separated or bracket
notation are not supported.
- name: ip_address
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by IP address or IP range (if CIDR notation is used).
If CIDR notation is not used, a /32 for IPv4 or /128 for IPv6 is
assumed.
Examples of range based queries: 10.0.0.0/24, 192.168.0.1/32
+++ Multiple IP addresses can be provided using the repeated keys+ syntax. For example,+ `ip_address=192.168.0.1&ip_address=10.0.0.0/24`, will match events+ with either IP address or range. Other notations like+ comma-separated or bracket notation are not supported.
- name: asn
in: query
schema:
type: string
description: >
@@ -1533,22 +1543,32 @@
This corresponds to the `ip_info.(v4|v6).asn` property in the
response.
- name: linked_id
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by your custom identifier.
You can use [linked
Ids](https://docs.fingerprint.com/reference/js-agent-v4-get-function#linkedid)
to associate identification requests with your own identifier, for
example, session Id, purchase Id, or transaction Id. You can then
use this `linked_id` parameter to retrieve all events associated
with your custom identifier.
+++ Multiple linked Ids can be provided using the repeated keys syntax.+ For example, `linked_id=session-1&linked_id=session-2`, will match+ events with a linked Id of `session-1` or `session-2`. Other+ notations like comma-separated or bracket notation are not+ supported.
- name: url
in: query
schema:
type: string
description: |
--- a/schemas/fingerprint-server-api-v4.yaml+++ b/schemas/fingerprint-server-api-v4.yaml@@ -413,18 +413,28 @@
will match events with a Bot Info Name of `ChatGPT Agent` or
`Bedrock AgentCore`. Other notations like comma-separated or bracket
notation are not supported.
- name: ip_address
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by IP address or IP range (if CIDR notation is used).
If CIDR notation is not used, a /32 for IPv4 or /128 for IPv6 is
assumed.
Examples of range based queries: 10.0.0.0/24, 192.168.0.1/32
+++ Multiple IP addresses can be provided using the repeated keys+ syntax. For example,+ `ip_address=192.168.0.1&ip_address=10.0.0.0/24`, will match events+ with either IP address or range. Other notations like+ comma-separated or bracket notation are not supported.
- name: asn
in: query
schema:
type: string
description: >
@@ -432,22 +442,32 @@
This corresponds to the `ip_info.(v4|v6).asn` property in the
response.
- name: linked_id
in: query
+ style: form
schema:
- type: string+ type: array+ items:+ type: string
description: >
Filter events by your custom identifier.
You can use [linked
Ids](https://docs.fingerprint.com/reference/js-agent-v4-get-function#linkedid)
to associate identification requests with your own identifier, for
example, session Id, purchase Id, or transaction Id. You can then
use this `linked_id` parameter to retrieve all events associated
with your custom identifier.
+++ Multiple linked Ids can be provided using the repeated keys syntax.+ For example, `linked_id=session-1&linked_id=session-2`, will match+ events with a linked Id of `session-1` or `session-2`. Other+ notations like comma-separated or bracket notation are not+ supported.
- name: url
in: query
schema:
type: string
description: |
🚀 Following releases will be created using changesets from this PR:
fingerprint-pro-server-api-openapi@3.4.0
Minor Changes
Add proxy, proxy_confidence, proxy_details, vpn, vpn_confidence, and vpn_methods to EdgeResponse (2d4f791)
events: Add battery_level and battery_low_power_mode to RawDeviceAttributes (ba43bc1)
Added VPN mlScore and mlPrediction to v3 events and events search (2d17209)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR automatically updates the OpenAPI schema.
Changes
5 file(s) modified, 1 file(s) added
Modified files
schemas/components/schemas/EdgeResponse.yamlschemas/paths/edge.yamlschemas/paths/events.yamlschemas/paths/examples/edge/analyze_200.jsonschemas/paths/examples/edge/analyze_200_non_bot.jsonAdded files
schemas/paths/examples/edge/analyze_200_proxy.jsonNote for reviewers: Please review the schema changes.
You likely need to manually add a changeset file to this branch before merging.