RestCase

[RestCase @RestCaseApi]

Security-first API Design https://t.co/CsQGnDaxPU

[DataEase AI @dataease_ai]

We asked AI for brand names and got: FlowSync, DataNest, BrandWise.

Tagline: "Smart tools for modern teams."

Clean. Pronounceable. Completely forgettable.

AI is trained on what exists, so unguided it hands you the category average. That's the opposite of what branding is for.

AI does the labor. You keep the judgment.
https://t.co/H2IjCZhI8V

[DataEase AI @dataease_ai]

Stop buying three frameworks for AI search.
SEO, AEO, GEO are not three strategies.

They are three layers of one system:
SEO = access
AEO = extraction
GEO = interpretation

One clear story about your brand, told consistently enough that machines at every layer reach the same conclusion.

https://t.co/4F5zMBZAvM

[RestCase @RestCaseApi]

@apievangelist We are currently working on the public API for controlling many aspects, connecting CICD and doing integrations. But it is not complete yet.

[RestCase @RestCaseApi]

@apihandyman 404 in case the resource does not exists and never existed. 410 in case it existed and was deleted (soft delete or something) and you allow to undelete.

[API Evangelist @apievangelist]

Remember, the @OpenApiSpec technical developer community is tomorrow 9:00 AM PDT / 6:00 PM CET and is open to the public -- come join the conversation around the future of the specification!

[Antón @antonmry]

Kowl is an Apache Kafka Web UI for exploring messages, consumers, configurations and more with a focus on a good UI & UX.

And it's open source 🌶️🌶️🌶️

https://t.co/l887EqCKRF

[Kevin Swiber @kevinswiber]

Okay, so if you're thinking to yourself, "To build tooling around OpenAPI is no big deal. How big can the spec be?" lemme just stop you right there. I've built a bunch of tools for OpenAPI but nothing this comprehensive before. I'm at 1500 lines just defining the grammar.

[Mike Ralphson @PermittedSoc]

This is HUGE. #GitHub #markdown #ToC

[API Evangelist @apievangelist]

Just talked with the KrakenD (@devopsfaith) folks about their open source API Gateway -- interesting to think about as part of the overall evolution and renewed investment in the API management space occurring right now.

[API Evangelist @apievangelist]

The @OpenApiSpec "Overlays" proposal being discussed today on the weekly TSC meeting - https://t.co/zLmTNglqOo

[Microcks @microcksio]

Microcks is the1⃣st tool to support @OpenApiSpec v3.1 in the Mocking and Testing sections of https://t.co/Yc00kg1ozA !
👉 https://t.co/QHfoctOkGQ

[ApiBldr @ApiBldr]

#apibldr now supports visual design for both #OpenAPI and #AsyncAPI 👍. Give it a try https://t.co/oXcq9S6Bpq

[RestCase @RestCaseApi]

Top 5 Security Issues in Public APIs and How to solve them https://t.co/ryzBxhGkzr

[Microcks @microcksio]

@AsyncAPISpec @lbroudoux And this was really easy 😉 Happy to grow the @AsyncAPISpec ecosystem!

[Microcks @microcksio]

📣 We're thrilled to release Microcks 1.0.0 with async #API support! This makes @microcksio the perfect tool for designers, providers & consumers to easily iterate using @AsyncAPISpec, @OpenAPISpec or legacy #soap services. Read 👉 https://t.co/7vGMr1UF1V cc @fmvilas @derberq

[Lorna Mitchell @lornajane]

You can do so many GREAT things with an OpenAPI spec, but how do you build the spec in the first place? Here's a blog post to walk you through a very simple spec for a very simple API, hope it helps! https://t.co/fnVcAs89dp Questions welcome as always :)

[Product Hunt Hi @ProductHuntHi]

@RestCaseApi ApiBldr just reached 100 upvotes. 😻 https://t.co/opzS43zBli

Add the badge to your site: https://t.co/xxWbYETZvp