#httpapi — Public Fediverse posts

#AIagents now have their own space-based #MMO called #SpaceMolt, designed exclusively for artificial intelligence. The game lets AI agents connect via #MCP, #WebSocket, or #HTTPAPI to mine asteroids, trade, explore, form factions, and engage in simulated combat across 505 star systems. Humans are reduced to spectators watching AI play with itself. https://arstechnica.com/ai/2026/02/after-moltbook-ai-agents-can-now-hang-out-in-their-own-space-faring-mmo/?eicker.news #tech #media #news

I found this an interesting approach to HTTP clients for Python: https://paulwrites.software/articles/python-api-clients

#Python #HTTP #WebDev #WebAPI #HTTPAPI

New one up 🗞️

"Adopting Problem Details for HTTP APIs"

In which I rant a bit, but also provide a glimpse into how we're approaching it at work.

#OpenApi #HttpApi #ProblemDetails #DotNet #CSharp

https://blog.codingmilitia.com/2025/07/15/adopting-problem-details-for-http-apis/

GitHub have come aboard the Kiota train for the future of their API client libraries. https://github.blog/2024-01-03-our-move-to-generated-sdks/ #kiota #httpapi

I know this looks right...
/customers/{customer-id}
but you really should do this
/customers/{customer_id}
because:
a) the first is invalid according to RFC6570 and
b) many programming languages don't allow dashes in variable names.
#httpapi

Consistent API design doesn't mean making everything fit in predefined boxes. It means reusing boxes where the scenario fits. If it doesn't, don't force it. #httpapi

I have updated the progress graphs of the IETF httpapi working group documents. https://ietf-wg-httpapi.github.io/

It is great to see us picking up steam and we now have three documents that have moved past Working Group Last Call with one more that is really close to going into WGLC. Thank you to all document editors and contributors.

You can see the issues we are working through listed on our GitHub project page https://github.com/orgs/ietf-wg-httpapi/projects/1 #ietf #httpapi

Evolving your RESTful APIs, a step-by-step approach https://blog.frankel.ch/evolve-apis/

#API #HTTPAPI #RESTAPI #fromthearchives

I did it! I got the blog up and running again, as well as an Atom feed that actually works.

This blog post is a continuation of my advocacy for using the path hierarchy of a URL as a key piece of your API design and developer experience.

https://apievolution.tavis.ca/posts/2023/the-majesty-of-trees/

#httpapi #openapi #kiota

Updated the #openapi based #httpapi visualizer to use some shapes for better accessibility. Some more examples here https://github.com/darrelmiller/openapi-collection/tree/main/ApiDiagrams

I built a thing that renders a diagram of an #httpapi from #openapi. Here is what the OpenAI API looks like.

Ah, the magic of standards. Thanks to #OpenTelemetry we can instrument #HTTPAPI client code generated from #kiota and show the traces in whatever tool you prefer. Here's a trace of the C# client from https://github.com/APIPatterns/Moostodon in #AzureMonitor

RT @hpgrahsl

Finally I released the long overdue v0.3.0 for #Kryptonite4Kafka which adds #ksqlDB #UDFs to do field-level 🔒 cryptography 🔓 in #SQL.

Basic documentation here https://github.com/hpgrahsl/kryptonite-for-kafka/blob/master/ksqldb-udfs-kryptonite/README.md

Also it's the last release before introducing the #HttpAPI as a new integration option.

RT @hpgrahsl

Finally I released the long overdue v0.3.0 for #Kryptonite4Kafka which adds #ksqlDB #UDFs to do field-level 🔒 cryptography 🔓 in #SQL.

Basic documentation here https://github.com/hpgrahsl/kryptonite-for-kafka/blob/master/ksqldb-udfs-kryptonite/README.md

Also it's the last release before introducing the #HttpAPI as a new integration option.

RT @hpgrahsl

Finally I released the long overdue v0.3.0 for #Kryptonite4Kafka which adds #ksqlDB #UDFs to do field-level 🔒 cryptography 🔓 in #SQL.

Basic documentation here https://github.com/hpgrahsl/kryptonite-for-kafka/blob/master/ksqldb-udfs-kryptonite/README.md

Also it's the last release before introducing the #HttpAPI as a new integration option.

RT @hpgrahsl

Finally I released the long overdue v0.3.0 for #Kryptonite4Kafka which adds #ksqlDB #UDFs to do field-level 🔒 cryptography 🔓 in #SQL.

Basic documentation here https://github.com/hpgrahsl/kryptonite-for-kafka/blob/master/ksqldb-udfs-kryptonite/README.md

Also it's the last release before introducing the #HttpAPI as a new integration option.

RT @hpgrahsl

Finally I released the long overdue v0.3.0 for #Kryptonite4Kafka which adds #ksqlDB #UDFs to do field-level 🔒 cryptography 🔓 in #SQL.

Basic documentation here https://github.com/hpgrahsl/kryptonite-for-kafka/blob/master/ksqldb-udfs-kryptonite/README.md

Also it's the last release before introducing the #HttpAPI as a new integration option.

📢 #HttpAPI for #Kryptonite for #Kafka starts to take shape. Screenshot shows partially encrypted JSON record being decrypted using cURL against the API. 🤩Any language/runtime will be able to use this for client-side field-level 🔒 #cryptography 🔓for #ApacheKafka