Skip to main content

Documentation Index

Fetch the complete documentation index at: https://newscatcherinc-docs.mintlify.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

This guide explains how to effectively report bugs and issues with the NewsCatcher APIs to ensure quick resolution and improve your experience.

​
Before you report

Before submitting a bug report, take the following steps to ensure efficient resolution:
  • Check documentation: Review the API Reference to verify you’re using parameters correctly and that you understand expected behaviors.
  • Verify API usage: Double-check that you’re using the correct headers, parameters, and payload formats according to our documentation.
  • Check status page: Visit our status page to see if there are any known issues or maintenance activities affecting the service.
  • Try our debugging tools: Use our Postman collections or the API playground in our documentation to verify if the issue can be reproduced with different tools.
  • Examine your code: Double-check your implementation to ensure the issue isn’t in your integration code.
Many reported “bugs” turn out to be integration issues that can be resolved through proper configuration or implementation. Testing with Postman often helps identify these cases quickly.

​
Where to report bugs

You can report bugs through the following official channels:

Customer Portal

Our preferred channel for bug reports with structured templates and ticket tracking

Email Support

Alternative channel for bug reports and general support

Dedicated Slack

For eligible customers with dedicated Slack channel access (based on plan tier)

GitHub Issues

Review the current issues and open a new one if needed (for SDK-related bugs only)
Our Customer Portal is the recommended channel as it automatically creates tickets in our internal tracking system, allowing for faster processing and resolution.

​
How to report effectively

When reporting a bug, include the following information to help us identify and fix the issue quickly:
1

Include the correlation ID

Every API response includes a unique correlation-id in the headers. This ID is essential for us to trace your request through our system.
Here’s how to find it:
curl -i https://v3-api.newscatcherapi.com/api/search
# Look for: correlation-id: 2697cebe-6f5c-46e0-9b99-81e8abe55522
2

Describe what happened vs. what you expected

Include a brief description of the following:
  • What you were trying to do
  • What actually happened
  • What you expected to happen instead
3

Provide request and response details

Provide the following information to reproduce the issue:
  • API endpoint and method (GET/POST)
  • Request parameters or payload
  • Error message and status code

​
Report template

Use this template when filing your report. It covers everything from the steps above.

​
Common issues and solutions

Before reporting a bug, check if your issue matches one of these common scenarios:

​
Using incorrect authentication header

We use x-api-token for authentication, not x-api-key: 
GET /v3/search HTTP/1.1
Host: api.newscatcherapi.com
x-api-token: YOUR_API_KEY

​
Malformed JSON payload causing 500 errors

If you receive a 500 Internal Server Error, check your request payload: 
{
  "q": "bitcoin",
  "from_": "30d",
  "countries": ["US", "CA"]
}
For security reasons, our API may return a generic 500 error for certain malformed payloads instead of detailed validation errors. Always validate your JSON before sending.

​
Bug report lifecycle

  1. Ticket creation: Your report is converted into a ticket in our internal tracking system.
  2. Initial assessment: Our support team performs an initial assessment to determine severity and priority.
  3. Investigation: Our engineering team uses the correlation ID to trace the issue through our logs and systems.
  4. Status updates: We keep you informed about the progress of your bug report through the same channel you used to report it.
  5. Resolution: Once resolved, we provide details about the fix and when you can expect it to be deployed.

​
Issue priority and response times

Priority is determined by two factors: urgency (how quickly the issue affects your operations) and impact (the scope and severity of the effect on service functionality). Knowing these levels helps you set expectations for response and resolution times.

​
Priority levels

PriorityDescriptionTarget Response TimeTarget Resolution Time
Priority 1Critical issue causing complete service unavailability with no workaround1 hourWithin 12 hours
Priority 2Significant issue with major impact; service usable but seriously impaired4 hours2 business days
Priority 3Moderate issue with acceptable workarounds available12 hours5 business days
Priority 4Minor issue with minimal impact1 business dayPlanned
Priority 1 issues should be reported by phone in addition to creating a ticket to ensure immediate attention. Standard support hours are 8am–5pm on business days in your principal location.
When reporting a bug, you can suggest a priority level based on the criteria above, but our support team makes the final determination after a technical assessment.

​
Debugging tools

We provide several tools to help you debug issues before reporting them:

Postman Collections

Pre-configured request collections for all our APIs with examples

API Playground

Interactive API testing tool available directly in our documentation

Documentation AI Assistant

To use our AI chat assistant, type your question in the search bar (⌘K)

Status Page

Real-time service status and incident history

​
See also