Sending Signals
20 March 2025
- Create a Signal
- Post Attributes
- signal - mediumstring
- report_date - date time
- abuse_type - string
- predictive - boolean (optional)
- confidence_score - integer (optional)
- signal_type - string (optional)
- List all of the Signals you have sent
- Get Attributes
- limit - integer
- offset - integer
- sort - string
- filter_{COLUMNAME} - string
post - https://signals.gse.live/report/signal
Create a Signal
Insert a set of new rows to the Signal feed
Post Attributes
signal - mediumstring
The signal you want to share
report_date - date time
Date & time the signal was reported.
abuse_type - string
The type of abuse this signal represents. Must be one of the following types...
Types
cloaking - Use this for Cloaking Identifiers
exploit - Use this for Exploit Identifiers
malware - Use this for Malware Identifiers
phishing - Use this for Phishing Identifiers
piracy - Use this for Piracy Identifiers
scam - Use this for Scam identifiers
spam - Use this for Spam identifiers
If you would like to send us a different abuse type, please contact us
predictive - boolean (optional)
An indication that this signal was generated using an algorithm rather than confirmed report.
confidence_score - integer (optional)
Number between 0-100. A score of 100 would indicate the highest confidence in this signal
signal_type - string (optional)
The type of signal. If supplied, must be one of the following...
Type
url - https://signalexchange.test/pathname
hostname - subdomain.signalexchange.test
domain name - signalexchange.test
ip address - 123.45.67.189
If not supplied we will attempt to detect this.
If you would like to send us a different signal type, please contact us
get - https://signals.gse.live/report/signal
List all of the Signals you have sent
Return all of the imported signals you have uploaded via your account.
Get Attributes
limit - integer
Limit the number of results to the supplied number
Defaults to 50. Max 10000
offset - integer
Offset the results by the supplied number
Defaults to 0
sort - string
Sort the results by supplying a column name and direction. eg signal | desc
filter_{COLUMNAME} - string
Filtering of the returned data can be effected by supplying parameters of the format filter_COLUMNNAME. The parameter value can either be simply a value for exact match filtering or a value followed by a | and a match type which should be one of the following values:
eq - for an equals match
neq - for a not equals match
null - for a null match
notnull - for a not null match
gt - for a greater than match
lt - for a less than match
gte - for a greater than or equals match
lte - for a less than or equals match
startswith - for a string that starts with match
endswith - for a string ends with match
contains - for a string contains match
Example: filter_signal=somesignal|contains
- Create a Signal
- Post Attributes
- signal - mediumstring
- report_date - date time
- abuse_type - string
- predictive - boolean (optional)
- confidence_score - integer (optional)
- signal_type - string (optional)
- List all of the Signals you have sent
- Get Attributes
- limit - integer
- offset - integer
- sort - string
- filter_{COLUMNAME} - string