To use this feature, you must have a Pulsedive Feed plan.
Your export access and available options are determined by your plan.
Before You Begin
You’ll need your Pulsedive API key. Find it on your account page. Not sure which format to use? Visit Choose an Export Format.Get a CSV Export
Build your Direct URL
Your Direct URL encodes your API key and chosen filters as query parameters.
Construct the URL manually using the parameters in CSV Export or use the download form to configure and generate it.
Pull your export
Go to your Direct URL to download your CSV:To automate ingestion, point your tooling at the Direct URL on your chosen schedule.
To learn more, visit Automate Your Export.
Get a STIX/TAXII Export
STIX/TAXII 2.1 export is available on Standard and Complete Feed plans.
Discover the server
Query the discovery endpoint to confirm your authentication and find available API roots.
Authenticate using HTTP Basic Auth with A successful response returns the available API roots and server information.
To learn more, visit Authentication.
taxii2 as the username and your API key as the password:Browse collections
Query the collections endpoint to find which collections contain the data you need.
Pulsedive provides separate collections for indicators and threats.The response includes each collection’s ID, title, and description.
Use the collection ID in the next step to retrieve objects.
To learn more, visit Collections.
Retrieve objects
Query a collection’s objects endpoint using the collection ID from the previous step.
Use filter parameters to limit results by risk level, indicator type, timestamps, and retirement status.For large collections, use the
next pagination token from each response to retrieve the next page.
To learn more, visit Filtering and Pagination.Troubleshooting
CSV export failed
If a CSV pull fails, retry the same Direct URL. The download will restart and pull the full dataset again with the configured filters. If the export consistently fails, contact Pulsedive Support.STIX/TAXII pull failed
TAXII is more fault-tolerant than CSV. If a pull fails mid-stream, you can resume from where you left off using a timestamp or thenext pagination token from your last successful response, without restarting the full export.
To learn more, visit Pagination.
If you continue to have issues, contact Pulsedive Support.