From a9027f4ab8a25313ded9f798589455f47cd44311 Mon Sep 17 00:00:00 2001 From: root-Brainoverflow Date: Mon, 13 Apr 2026 14:30:55 +0900 Subject: [PATCH] fix: use /pulses/activity endpoint instead of /pulses/subscribed The /pulses/subscribed endpoint consistently returns 504 Gateway Timeout errors, making the SDK unusable for fetching subscribed pulses. The /pulses/activity endpoint provides the same data and works reliably. Testing shows: - /pulses/subscribed: 504 timeout (30+ seconds) - /pulses/activity: Success (< 2 seconds, returns all pulses) This change maintains backward compatibility as both endpoints return the same data structure. --- OTXv2.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OTXv2.py b/OTXv2.py index 9c14f6f..bcca640 100755 --- a/OTXv2.py +++ b/OTXv2.py @@ -22,7 +22,7 @@ # API URLs API_V1_ROOT = "/api/v1" # API v1 base path -SUBSCRIBED = "{}/pulses/subscribed".format(API_V1_ROOT) # pulse subscriptions +SUBSCRIBED = "{}/pulses/activity".format(API_V1_ROOT) # pulse subscriptions EVENTS = "{}/pulses/events".format(API_V1_ROOT) # events (user actions) SEARCH_PULSES = "{}/search/pulses".format(API_V1_ROOT) # search pulses SEARCH_USERS = "{}/search/users".format(API_V1_ROOT) # search users