Contact
Questions, bug reports and billing help all start with an email. A few details in your first message let us answer without back and forth.
Email support
Write to [email protected]. This is a placeholder address until the mailbox is live. We read every message and reply by email.
What to include
The more of this you send, the faster we can help:
- The request ID. Every response includes it in the
X-Request-Idheader, and error bodies include it asrequest_id. It lets us find your exact call. - The endpoint and parameters you used, for example
/v1/storieswith your filters. You can remove your API key. - What you expected and what happened instead, including the status code and error code.
- Your plan and where you subscribed, such as the RapidAPI listing or direct.
- The time of the call and your time zone.
Please never send your full API key or any password. If you think a key has leaked, say so and we will help you replace it.
Before you write
Many questions are answered by a response itself. Errors use one shape, with a code, a message and, for bad parameters, a list of allowed values. A 403 plan_restriction means the request is outside your plan, and the error lists what is allowed. A 429 means a quota or rate limit was reached; the X-Quota-Remaining and X-Quota-Reset headers show where you stand.
Useful pages
- Documentation: quickstart, filters, endpoints, errors and monitors.
- Live console: try a query without writing code.
- Pricing: plans, limits and how credits are counted.
- Changelog: what changed and when.
- Overview of the Latest News API.
Topics we can help with
- Using the API: filters, pagination, fields, numbers and counts.
- Plans and billing: limits, upgrades, overage and how a marketplace subscription maps to a plan.
- Agents and MCP: connecting the server and choosing tools.
- Data questions: a story that looks wrong or incomplete. Send the story ID.
- Privacy requests: see the privacy policy.
Billing and subscriptions
If you subscribed through a marketplace, plan changes, cancellations and invoices are handled there. Write to us when your plan does not match what you pay for, when a limit looks wrong, or when you need a quota that no listed plan offers. Tell us your current plan and the monthly volume you expect, and we will point you to the best fit.
Reporting a data problem
If a story looks wrong, send its ID, the field you question and what you would expect. Stories update as more facts come in, so we check the current record. Remember that facts are written automatically and can be incomplete, as described in the terms.
Feature requests
Tell us what you are building and what is missing. Short, concrete examples help most, such as the query you wish you could run.
Legal
For questions about use of the data, see the terms of use. Both the terms and the privacy policy are drafts and will be reviewed before launch.
Questions
How do I contact LatestNewsAPI support?
Email [email protected] (a placeholder address until the mailbox is live). Include your request ID and the endpoint you called.
Where do I find the request ID?
In the X-Request-Id response header, and in the request_id field of any error response.
Should I send my API key?
No. Never send your full key or any password. If a key has leaked, tell us and we will help you replace it.
Where can I see what changed in the API?
The changelog in the documentation lists each release.