API

Approximately 19% of mobile and web APIs still allow HTTP fallback instead of enforcing TLS, leaving sensitive data and authentication credentials exposed to interception.

The robustness of agentic solutions depends on API quality used by MCP servers. MCP tools reference individual API endpoints, and poor API quality directly reduces the LLM client's ability to accurately discover and execute user prompts.

Concurrent API operations within a Neon project on different branches could trigger a "project already has running operations" error, where one branch operation would block others. While concurrency limits have been increased, developers still need to implement retry functionality to handle rare failures.

Making different systems work together through APIs creates persistent challenges including version management, authentication complexity, data format mismatches, and webhook reliability issues. These problems span multiple systems and are difficult for single vendors to solve comprehensively.

When API providers deprecate fields (e.g., replacing `name` with `first_name` and `last_name`), dependent code breaks immediately. Developers must update SDKs, fix code, test, and redeploy—a reactive cycle that causes unplanned downtime and rework.

Most API documentation is written for human developers and lacks semantic descriptions needed for AI agents to understand intent. This documentation-understanding gap makes it difficult for LLMs to correctly interpret and use APIs.

APIs are difficult to test compared to web applications because A/B testing different API design approaches is impractical. Developers cannot send out multiple API samples and expect users to program against all of them, making it challenging to validate API design decisions before widespread deployment.

Self-healing mechanisms work only for schema changes but fail for semantic API changes. The system may incorrectly 'heal' when the real issue is bad user input, leading to silent failures.

JavaScript email libraries maintain broken documentation with outdated links, 404 errors, and circular help pages, forcing developers to abandon the libraries and interact directly with APIs instead.

API provides limited statistics for error rate analysis. More granular error rate metrics would be helpful. Limited programmatic access to metrics compared to competitor offerings.

Sentry API clients lack native asynchronous communication support. Custom implementation required. Additionally, filtering by fingerprints is not possible despite fingerprint tracking being available.