Mathstodon

1 post1 participant0 posts today

Gerbrand van DieyenE.g. something to describe data-format in a programming language agnostic way. With tool support for many popular programming languages, and ways to generate document. And easy enough to use.<a href="https://fosstodon.org/tags/openapi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openapi</a> is very popular but that's more focused on endpoints and operations, but lacking on data-format. And for my particular problem the data-format is more important than the operations.

Markus EiseleImplementing Zalando RESTful API Guidelines with Quarkus <a href="https://myfear.substack.com/p/implementing-zalando-restful-api" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://myfear.substack.com/p/implementing-zalando-restful-api</a> <a href="https://mastodon.online/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> <a href="https://mastodon.online/tags/Quarkus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quarkus</a> <a href="https://mastodon.online/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://mastodon.online/tags/Zalando" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zalando</a>

Gloria Ciavarrini :redhat:🚀 Join me at DevFest Pisa 2025 where I’ll be sharing insights on how to elevate API experiences! 🎤My talk, “Overlay and Arazzo: From API Definitions to API Experiences” will explore how we can transform APIs into seamless user experiences.📅 When: April 12, 2025 🕓 Time: 11:40 AM 📍 Where: MACC - Pisa - Italy 🗓️ Schedule: <a href="https://devfest.gdgpisa.it/talk/overlay-and-arazzo-from-api-definitions-to-api-experiences/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://devfest.gdgpisa.it/talk/overlay-and-arazzo-from-api-definitions-to-api-experiences/</a>Hope to see you there! 🎉<a href="https://fosstodon.org/tags/DevFestPisa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevFestPisa</a> <a href="https://fosstodon.org/tags/TechTalks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechTalks</a> <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://fosstodon.org/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://fosstodon.org/tags/Overlay" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Overlay</a> <a href="https://fosstodon.org/tags/Arazzo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Arazzo</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a>

Markus EiseleSpec-First or Code-First? Choosing Your OpenAPI Strategy with Quarkus vs. Spring <a href="https://myfear.substack.com/p/spec-first-or-code-first-choosing" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://myfear.substack.com/p/spec-first-or-code-first-choosing</a> <a href="https://mastodon.online/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> <a href="https://mastodon.online/tags/Quarkus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quarkus</a> <a href="https://mastodon.online/tags/APIDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIDesign</a> <a href="https://mastodon.online/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a>

happyborgGood progress on the <a href="https://fosstodon.org/tags/dweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dweb</a> REST APIs and improvements to the <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> docs today, all with the help of <a href="https://fosstodon.org/tags/actix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#actix</a> and <a href="https://fosstodon.org/tags/utoipa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipa</a> BTW <a href="https://fosstodon.org/tags/SwaggerUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SwaggerUI</a> is really cool A few days ago I knew nothing about these but now I have a working API that is documented and can be tested live while reading those docs.Someone asked if I might support <a href="https://fosstodon.org/tags/GraphQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GraphQL</a> but I haven't looked into that. Convince me that I should!

Miguel Afonso Caetano"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."<a href="https://gist.github.com/briandominick/3ffab6be460fbde799aa34e0a42a4299" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gist.github.com/briandominick/3ffab6be460fbde799aa34e0a42a4299</a><a href="https://tldr.nettime.org/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#API</a> <a href="https://tldr.nettime.org/tags/APIs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIs</a> <a href="https://tldr.nettime.org/tags/APIDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIDesign</a> <a href="https://tldr.nettime.org/tags/REST" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#REST</a> <a href="https://tldr.nettime.org/tags/APIDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIDocumentation</a> <a href="https://tldr.nettime.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://tldr.nettime.org/tags/DocsAsCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DocsAsCode</a> <a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

happyborgToday I added <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> documentation to <a href="https://fosstodon.org/tags/dweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dweb</a> for building <a href="https://fosstodon.org/tags/RESTful" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RESTful</a> <a href="https://fosstodon.org/tags/p2p" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#p2p</a> web apps using your favourite web framework, or no framework at all. All I have to do now is add more APIs!But tbh, that's easy. The hardest part is actually the documentation. :rofl: So to make it more fun I'm adding the APIs need to enhance my <a href="https://fosstodon.org/tags/Fileman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fileman</a> <a href="https://fosstodon.org/tags/Svelte" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Svelte</a> demo.So next is image preview which means adding /dweb-0/file-get <a href="https://fosstodon.org/tags/Decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Decentralization</a> <a href="https://fosstodon.org/tags/dApps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dApps</a> <a href="https://fosstodon.org/tags/WebApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebApp</a> <a href="https://fosstodon.org/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#API</a>

LornaJane Change the fields returned by your API by offering more representations of the resources. This under-appreciated feature of API design can help teams to get the best from their API for multiple use cases, without the need to switch to GraphQL. <a href="https://lornajane.net/posts/2025/better-rest-before-graphql" class="" rel="nofollow noopener noreferrer" target="_blank">https://lornajane.net/posts/2025/better-rest-before-graphql</a>

happyborgHaving played a bit I'm now adding <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> docs with <a href="https://fosstodon.org/tags/Swagger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Swagger</a> UI to <a href="https://fosstodon.org/tags/Autonomi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Autonomi</a> dweb using <a href="https://fosstodon.org/tags/utoipa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipa</a> and <a href="https://fosstodon.org/tags/utoipauto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipauto</a>.EDIT: switched from <a href="https://fosstodon.org/tags/utoipauto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipauto</a> to <a href="https://fosstodon.org/tags/utoipa_actix_web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipa_actix_web</a>I'm neither a user nor, until now a builder of HTTP APIs so stumbling around, but these crates do a decent job of being usable even to a novice.I really shouldn't be let loose with all this :rofl: <a href="https://fosstodon.org/tags/Rustlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rustlang</a> <a href="https://fosstodon.org/tags/REST" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#REST</a> <a href="https://fosstodon.org/tags/WebAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebAPI</a>

happyborgBaby steps building my first <a href="https://fosstodon.org/tags/REST" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#REST</a> API into <a href="https://fosstodon.org/tags/dweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dweb</a> using <a href="https://fosstodon.org/tags/actix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#actix</a> and now wondering how to document it.First impression is <a href="https://fosstodon.org/tags/utoipa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#utoipa</a> (more active and possibly suitable than <a href="https://fosstodon.org/tags/apisto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apisto</a>) so I'll try the former first.Opinions and experiences with these and other options welcome! <a href="https://fosstodon.org/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://fosstodon.org/tags/Rustlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rustlang</a>

:rss: Qiita - 人気の記事【Hono】作成したAPIをSwagger UI上で動作確認したい <a href="https://qiita.com/ryouryou_34/items/a5b566e0feb6457275cb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://qiita.com/ryouryou_34/items/a5b566e0feb6457275cb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items</a><a href="https://rss-mstdn.studiofreesia.com/tags/qiita" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qiita</a> <a href="https://rss-mstdn.studiofreesia.com/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TypeScript</a> <a href="https://rss-mstdn.studiofreesia.com/tags/swagger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swagger</a> <a href="https://rss-mstdn.studiofreesia.com/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Hono" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hono</a>

Markus EiseleUnlock the Power of Your APIs: A Hands-On Introduction to Quarkus OpenAPI with Swagger Effortless API Documentation in Quarkus: Getting Started with OpenAPI <a href="https://open.substack.com/pub/myfear/p/unlock-the-power-of-your-apis-a-hands" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://open.substack.com/pub/myfear/p/unlock-the-power-of-your-apis-a-hands</a> <a href="https://mastodon.online/tags/Quarkus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quarkus</a> <a href="https://mastodon.online/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> <a href="https://mastodon.online/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> <a href="https://mastodon.online/tags/Swagger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Swagger</a> <a href="https://mastodon.online/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#API</a>

Ben RamseyHey, folks! I’m looking for a Staff Software Engineer to join my team (API Core) at <a href="https://phpc.social/tags/Mailchimp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailchimp</a>.Some of the things we work on: <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PHP</a>, <a href="https://phpc.social/tags/REST" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#REST</a>, <a href="https://phpc.social/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a>, <a href="https://phpc.social/tags/OAuth2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OAuth2</a>, <a href="https://phpc.social/tags/APIGovernance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIGovernance</a>, and more.We are stewards of our public <a href="https://phpc.social/tags/APIs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIs</a>, and we collaborate with other capabilities teams to ensure APIs are developed according to our standards and processes. You would work directly with me on a daily basis.This position is in Atlanta or New York.<a href="https://jobs.intuit.com/job/atlanta/staff-software-engineer-api-core-team/27595/76329932512" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://jobs.intuit.com/job/atlanta/staff-software-engineer-api-core-team/27595/76329932512</a><a href="https://phpc.social/tags/GetFediHired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GetFediHired</a> <a href="https://phpc.social/tags/FediHire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediHire</a>

Hunter SkrasekIt's my first open source release in what feels like years, but I've published a new <a href="https://social.skrasek.us/tags/PHP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PHP</a> library for parsing <a href="https://social.skrasek.us/tags/openapi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openapi</a> Arazzo specifications into plain old PHP objects. I'm hoping to use this as the starting point for future <a href="https://social.skrasek.us/tags/arazzo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#arazzo</a> related packages, and looking forward to seeing what others may build with it. <a href="https://github.com/hskrasek/arazzo-parser/" rel="nofollow noopener noreferrer" target="_blank">https://github.com/hskrasek/arazzo-parser/</a>

LornaJane API reference documentation changed the way we built integrations, and eventually became part of the driving force for OpenAPI adoption and all the good tooling that flowed from it. As a developer experience specialist, I spend a lot of time thinking about how human users can work with the technical assets in a project. HTML-format API reference documentation does a great job of building that bridge when working on OpenAPI projects, but now I’m using Arazzo and it’s a very new standard with not nearly as many tools available for that format yet – so I built one. […] <a href="https://lornajane.net/posts/2025/markdown-mermaid-output-for-openapi-arazzo" class="" rel="nofollow noopener noreferrer" target="_blank">https://lornajane.net/posts/2025/markdown-mermaid-output-for-openapi-arazzo</a>

lornajaneGot completely carried away writing what was supposed to be a simple article on <a href="https://indieweb.social/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> linting and now I'm deep in Vacuum, Scalar, and Microcks features and it's GREAT. How's your Tuesday?

Fabio ManganielloI’ve recently taken a closer look at the <a class="hashtag" href="https://manganiello.social/tag/foursquare" rel="nofollow noopener noreferrer" target="_blank">#Foursquare</a> <a class="hashtag" href="https://manganiello.social/tag/api" rel="nofollow noopener noreferrer" target="_blank">#API</a> (updating the long unmaintained Platypush plugin, details on why coming soon).At first their new API versioning schema seemed a bit confusing (why would anyone use arbitrary <code>YYYYMMDD</code> strings as versions?), but a closer look at how they implemented it revealed a quite clever design decision:<blockquote>Versioning is controlled by the <code>v</code> parameter, which is a date that represents the “version” of the API for which you expect from Foursquare. It is designed to give developers the freedom to adapt to Foursquare API changes on their own schedule. The value of the v parameter is a date in YYYYMMDD format that lets you tell us “I’m prepared for API changes up to this date.”</blockquote>You know when you look at an engineering decision that is so elegant and obvious that you think “damn, how could nobody think of this before?”Nearly two decades spent managing <code>/v1</code>, <code>/v2</code>, <code>/v2.5</code>, <code>/v2.almost3</code>, <code>/v3</code>, managing migrations and deprecations, documenting breaking changes, introducing exponentially thicker layers of schemas and converters, and the obvious solution was just there under our nose.Why don’t you just start with defining the base schemas of your API objects at the time of their first release, and then every time you add, modify or delete a field, or change some return type, or add a value to an enum, you just version the change with a timestamp?Let the developer say “I understand the language that your API spoke 3 months ago”, and you just dynamically create the schemas, GraphQL or ORM snippets to parse requests and responses as of that date.No more breaking changes. No more forced migrations. No more boilerplate to explicitly convert payloads across different API versions.You construct the response by first applying the base schema, and then gradually patching it - just like you would do with a git rebase, or an ORM migration tool.A downside may probably be that you can never really delete a column from the db if it was ever used by any version of your API.And a challenge may also be to adapt tools like <a class="hashtag" href="https://manganiello.social/tag/openapi" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> / <a class="hashtag" href="https://manganiello.social/tag/swagger" rel="nofollow noopener noreferrer" target="_blank">#Swagger</a> that were designed around static schemas to also work with “dynamically versioned” selections.But to me the problems it solves far outweight the downsides.<a href="https://docs.foursquare.com/developer/reference/versioning" rel="nofollow noopener noreferrer" target="_blank">https://docs.foursquare.com/developer/reference/versioning</a>

lil5 :rustcrab: 🚲 🇳🇱<a href="https://github.com/lil5/ledgerbeetle/commit/ad9c85f14d7094c70d7712ba4f327526fea26641" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/lil5/ledgerbeetle/commit/ad9c85f14d7094c70d7712ba4f327526fea26641</a><a href="https://crates.io/crates/utoipa" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://crates.io/crates/utoipa</a>I started using utopia to generate the <a href="https://social.linux.pizza/tags/OpenAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAPI</a> document, its great!<a href="https://social.linux.pizza/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a>

Philipp :emacs: :nixos:It's such a shame that the "official" <a href="https://fosstodon.org/tags/openapi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openapi</a> generator for <a href="https://fosstodon.org/tags/haskell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#haskell</a> code doesn't generate proper union types. I mean, that's one of *the* defining features in Haskell.

John LeonardA coalition of European cloud providers, including Aruba, IONOS and Dynamo, has introduced the Sovereign European Cloud API (SECA), a new open standard for cloud infrastructure management.<a href="https://www.computing.co.uk/news/2025/cloud/european-cloud-providers-push-for-open-api-standard-amid-sovereignty-concerns" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.computing.co.uk/news/2025/cloud/european-cloud-providers-push-for-open-api-standard-amid-sovereignty-concerns</a><a href="https://mastodon.social/tags/seca" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#seca</a> <a href="https://mastodon.social/tags/cloudcomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudcomputing</a> <a href="https://mastodon.social/tags/technews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technews</a> <a href="https://mastodon.social/tags/europe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#europe</a> <a href="https://mastodon.social/tags/aruba" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aruba</a> <a href="https://mastodon.social/tags/ionos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ionos</a> <a href="https://mastodon.social/tags/dynamo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dynamo</a> <a href="https://mastodon.social/tags/openapi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openapi</a>

Recent searches

Search options

Administered by:

Server stats:

#openapi