> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulsedive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Feed

> Diagnose TAXII connectivity issues and errors when pulling a specific collection.

If you need to troubleshoot Pulsedive's TAXII server, explore these solutions to common issues.
If you don't find your issue here, check the [TAXII documentation](/taxii/overview) or reach out to [Support](/support).

## Why can't I connect to Pulsedive's TAXII server?

An API key is required for every TAXII request, including the free test collection, so a connection failure is almost always a credentials or plan mismatch rather than a server-side issue.

<Steps>
  <Step title="Confirm your plan covers what you are connecting to">
    The test collection only needs a free API key.
    Connecting to the indicator or threat collections needs a Pro plan or any level of Feed plan.
    If you need to export the full dataset rather than just connect and query, that requires a Standard or Complete Feed plan specifically.
  </Step>

  <Step title="Confirm your credentials">
    Username is always `taxii2`.
    Password is your Pulsedive API key, which you can find on your account page.
  </Step>

  <Step title="Match your authentication method to your client">
    Most TAXII clients expect HTTP Basic Authorization: base64-encode `taxii2:<YOUR_API_KEY>` into the `Authorization` header.
    If your client lets you enter username and password separately, use `taxii2` and your API key directly, it will encode this for you.
    Query string authentication (`?key=<YOUR_API_KEY>`) works too, but it is meant for testing and debugging, not production clients.
  </Step>

  <Step title="Test against the discovery endpoint">
    Send a request to `https://pulsedive.com/taxii2/` with your chosen auth method.
    Both Basic Auth and query string authentication should return the same response.
  </Step>
</Steps>

## Why am I getting an error when I try to pull a collection?

Collection errors usually trace back to a wrong ID or a plan mismatch, so start by confirming that you are using one of Pulsedive's three collection IDs:

| Collection | ID | Access level |
| - | - | - |
| Test data | `981c4916-ebb2-4567-aece-54ae970c4230` | Free with API key |
| Indicator data | `a5cffbfe-c0ff-4842-a235-cb3a7a040a37` | Pro or any Feed plan |
| Threat data | `dc9ecfa5-7769-4cf3-b699-38a9776b431d` | Pro or any Feed plan |

If the ID is correct, check what the error code is telling you:

* `400`: A filter parameter is malformed, most often a `match[]` value that doesn't match the expected format, or a bad timestamp in `added_after`.
* `401`: Your plan doesn't cover the collection you're requesting, or your credentials are wrong.
  Refer to the [Why can't I connect to Pulsedive's TAXII server?](#why-cant-i-connect-to-pulsedives-taxii-server) section.
* `404`: The collection ID itself is wrong.
  Collection IDs are fixed; double check it against the table above rather than a value from another TAXII source.

These collection IDs are hardcoded and won't change, so once a client is configured correctly, connectivity issues tend to come from plan or credential changes on your account rather than anything shifting on Pulsedive's end.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.