masto.es es uno de los varios servidores independientes de Mastodon que puedes usar para participar en el fediverso.
Bienvenidos a masto.es, el mayor servidor de Mastodon para hispanohablantes de temática general.

Administrado por:

Estadísticas del servidor:

1,9 K
usuarios activos

#apidesign

0 publicaciones0 participantes0 publicaciones hoy

"Traditional approaches to rate limiting APIs won’t work effectively for AI agent consumers, so some API providers have shifted to adaptive rate limiting (ARL). For example, DeepSeek employs a more dynamic and adaptive approach to rate limiting its API compared to other LLM API providers currently.

The concept of adaptive rate limiting isn’t new, but it’s evolving to address new API usage scenarios that include AI agents. Modern ARL involves a set of principles, tools, and techniques that allow systems to adjust rate limits dynamically based on context and real-time insights. It includes a combination of approaches:"

nordicapis.com/how-ai-agents-a

Nordic APIs · How AI Agents Are Changing API Rate Limit Approaches | Nordic APIs |AI agents are changing API usage patterns — here's how adaptive rate limiting helps handle their unpredictable, high-volume traffic.
#AI#AIBots#ARL

Goedemorgen! 🌞

Hebben jullie onze documentatie over API's al eens gebruikt?

🔌 Onze handleiding "Bouw een API" vertelt je over hoe je op basis van een OpenAPI Specification (OAS) een API bouwt. Het voordeel hiervan is dat je niet direct hoeft te coderen, maar dat je wel al omschrijft hoe de API er uit moet komen te zien.

developer.overheid.nl/kennisba

Mochten jullie feedback op het artikel hebben, een pull request/ issue inschieten mag altijd 🙋

github.com/developer-overheid-

developer.overheid.nlBouw een API | developer.overheid.nlHier leggen we uit welke stappen je kunt doorlopen om snel en efficiënt een nieuwe REST API te ontwikkelen. We gaan hierbij uit van een design first aanpak, dus we starten met het API design.

"API keys are foundational elements for authentication, but relying solely on them is inherently a risky proposal.

Firstly, there’s the reality that API keys are not securely designed — they were never meant to be used as the sole form of authentication, and as such, they aren’t really built for the task. These keys can often be easily stolen, leaked, or, in some cases (especially if generated incrementally), outright guessed. An API key is suitable for tracking usage but is poor for security.

There is also the additional reality that keys in their default state lack some critical functionality. There’s not a lot of verification built-in for identity management, and what does exist offers very little in the way of granular access control.

Ultimately, solely relying on API keys is a mistake common with novice developers but frighteningly common even in advanced products.

Best Practices
Instead of relying heavily on API keys as a sole mechanism, combine those keys with additional approaches such as OAuth 2.0 or mTLS. Implement rigorous expiration and rotation policies to ensure that keys which are made public are only useful for a short amount of time. Consider more advanced approaches, such as IP whitelisting or device fingerprinting, to add another layer of security atop the API key process."

nordicapis.com/9-signs-youre-d

Nordic APIs · 9 Signs You're Doing API Security Wrong | Nordic APIs |API security anti-patterns are common. From overreliance on API keys to a lack of rate limiting to no encryption, we explore the top ones.

"The accompanying diagram is intended to help you quickly decide how to document an API, but particularly a REST API. The first split is just to make sure you are looking for the right kind of API.

Here is some more context to help you decide on an approach and get started."

gist.github.com/briandominick/

GistAPI Documentation Decision MatrixAPI Documentation Decision Matrix. GitHub Gist: instantly share code, notes, and snippets.