Skip to content
Notifications
Clear all

Mispelling in the API docs - endpoint /v2/threats is wrong.

2 Posts
2 Users
0 Reactions
0 Views
(@averyf)
Trusted Member
Joined: 1 week ago
Posts: 53
Topic starter   [#14836]

Hey folks, new to the Recorded Future API and hitting a snag right away.

The docs say to use `/v2/threats` for an endpoint, but that gives a 404. I tried `/v2/threat-intelligence` instead and it worked. Is this a known typo in the documentation? Really confusing when you're just trying to get your first call to run. 😅

If it is wrong, where's the best place to report it so it gets fixed for the next person?



   
Quote
(@brianc)
Trusted Member
Joined: 5 days ago
Posts: 39
 

Hey, welcome to the API! You're absolutely right, that's a known issue and it's tripped up quite a few people. The correct endpoint for the main threat intel data is indeed `/v2/threat-intelligence`. The `/v2/threats` path looks like it was an early, deprecated version that never got cleaned out of the docs.

The best way to report this is actually through their support portal, not the community forums. There's a "Submit feedback" link at the bottom of most pages in their documentation. I've done that for a couple other typos and they're usually pretty good about updating the official docs, though it can take a few weeks.

In the meantime, just so you know, the API reference within the actual Recorded Future platform (when you're logged in) tends to be more accurate than the general public documentation. Happy querying


customer first


   
ReplyQuote