# OpenAPI Specification Published articles for OpenAPI Specification. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 10 Tips for Preparing APIs for Agentic Access DevFeed: [10 Tips for Preparing APIs for Agentic Access]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-08-27T11:40:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Artificial Intelligence](), [observability](), [Security](), [Architecture & Design](), [Cloudflare]() Tags: [agentic](), [agentic-ai](), [ai](), [ai-agents](), [api-best-practices](), [api-design](), [api-discovery](), [api-documentation](), [api-monitoring](), [api-security](), [apis](), [artificial-intelligence](), [blog](), [json-schema](), [oauth](), [observability](), [openapi-specification](), [security](), [workflows]() ### AI overview Ten ways to prepare APIs for agentic access by improving discovery, security, observability, workflows, and predictable design for AI agents. ### Source excerpt In May 2026, Cloudflare released a new tool called isitagentready.com. It analyzes a URL for everything an agentic AI would need to interact with a site and then returns a score out of 100. Even better still, it breaks down its assessment by category, letting you know how your site performs for discoverability, accessibility from ... ## How Fuzz Testing for APIs Is Evolving DevFeed: [How Fuzz Testing for APIs Is Evolving]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-08-21T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Testing](), [API](), [Large Language Model](), [Security](), [HTTP]() Tags: [api-security](), [api-testing](), [api-vulnerabilities](), [apis](), [artificial-intelligence](), [blog](), [http](), [llm](), [llms](), [open-source](), [openapi-specification](), [rest](), [security](), [testing](), [validation]() ### AI overview The article examines how API fuzz testing is evolving through the use of LLMs, OpenAPI Overlay, and automated security testing. It highlights the importance of generating suitable test data so HTTP requests can pass input validation and reach deeper security checks. ### Source excerpt Ahead of Nordic APIs Summit 2026, we check in with speaker Andrea Arcuri on how fuzz testing for APIs is evolving. "You cannot really check security properties if all your HTTP calls fail with a 4xx because your techniques can't generate the right test data to pass the first layer of input validation," answers Andrea ... ## Add API visualizations in Port with Swagger UI | Port DevFeed: [Add API visualizations in Port with Swagger UI | Port]() Original publisher: [Read original article]() Author: Dudi Elhadad Published: 2026-07-30T10:09:05Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [OpenAPI Specification](), [Markdown](), [Microservice](), [dev-tools]() Tags: [api](), [developer-portal](), [documentation](), [integration](), [markdown](), [openapi-specification](), [software-catalog](), [visualization]() ### AI overview Port adds visualization features to its software catalog and developer portal, including Markdown documentation, OpenAPI specifications rendered with Swagger UI, and embedded URLs. These features centralize documentation, API discovery, monitoring dashboards, and other developer tools in context, reducing search and context switching. ### Source excerpt Here are the visualization features we just added: Markdown documentation visualization, Open API - swagger and embedded URLs. ## Snyk Supercharges API Discovery with New Akamai Integration DevFeed: [Snyk Supercharges API Discovery with New Akamai Integration]() Original publisher: [Read original article]() Author: Nuno Loureiro Published: 2025-08-06T04:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [API](), [Application Security](), [snyk-platform](), [Security](), [OpenAPI Specification]() Tags: [2025](), [akamai](), [analysis](), [api](), [api-discovery](), [api-security](), [api-testing](), [apis](), [application-security](), [awareness](), [blog](), [co-created](), [efficiency](), [executive](), [integration](), [openapi](), [openapi-specification](), [platform](), [scanner](), [snyk](), [snyk-platform](), [testing](), [web]() ### AI overview Snyk and Akamai announced an integration that automates API discovery and schema ingestion. Akamai API inventories and schemas are added to Snyk API & Web so teams can turn discovered APIs into scannable targets with a single click, improving API security testing coverage and efficiency. ### Source excerpt Snyk and Akamai partner to streamline API security. This integration automates API discovery and schema ingestion from Akamai to power Snyk's DAST engine, boosting scan coverage and efficiency. ## AppLink Fundamentals III: Building with AppLink - Development Flow and Language Choices DevFeed: [AppLink Fundamentals III: Building with AppLink - Development Flow and Language Choices]() Original publisher: [Read original article]() Author: Ken W. Alger Published: 2025-07-31T15:00:35Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Development](), [Programming](), [OpenAPI Specification](), [Artificial Intelligence]() Tags: [apis](), [applink](), [development](), [engineering](), [extensions](), [heroku](), [integrations](), [languages](), [openapi](), [openapi-specification](), [programming](), [salesforce](), [tutorial]() ### AI overview This final AppLink Fundamentals article explains the development workflow for Salesforce extensions on Heroku, including local testing, managing changes to the OpenAPI specification, and choosing a programming language. It also covers Agentforce integrations and an automotive finance example involving real-time credit assessment, pricing rules, and PDF generation. ### Source excerpt This blog series has taken you on a journey through the world of AppLink, from its foundational concepts and core components in Heroku AppLink: Extend Salesforce with Any Programming Language, to a deep dive into its key integration patterns in AppLink Fundamentals I: AppLink Integration Patterns - Connecting Salesforce to Heroku Applications, and then we [...] The post AppLink Fundamentals III: Building with AppLink - Development Flow and Language Choices appeared first on Heroku. ## API Orchestration with Connectors - Thinking in Entities DevFeed: [API Orchestration with Connectors - Thinking in Entities]() Original publisher: [Read original article]() Author: Michael Watson Published: 2025-02-12T16:51:19Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [Orchestration](), [OpenAPI Specification](), [schema design](), [GraphQL]() Tags: [api](), [apollo-connectors](), [graphql](), [openapi](), [openapi-specification](), [orchestration](), [patterns](), [rest](), [schema-design](), [swagger]() ### AI overview This tutorial introduces API orchestration with Apollo Connectors for REST and explains how to identify entities in existing APIs before exposing them through a connector. It emphasizes using unique identifiers and preserving existing REST API domain definitions when designing the schema. ### Source excerpt Since we first announced Apollo Connectors for REST at GraphQL Summit 2024, there has been an enormous amount of excitement from the community to dive in. I've been working with dozens of Enterprises on their use cases from breaking apart existing monoliths to integrating multiple production OpenAPI specification endpoints. In my work, there have been some patterns that have emerged and I wanted to start a new blog series that helps share the happy path to building faster. ## Year in Review 2023 DevFeed: [Year in Review 2023]() Original publisher: [Read original article]() Author: Marcus Kohlberg Published: 2024-01-04T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [releases](), [Secrets Management](), [observability](), [Monitoring](), [OpenAPI Specification](), [Grafana](), [datadog]() Tags: [datadog](), [engineering](), [grafana](), [monitoring](), [observability](), [openapi-specification](), [releases](), [secrets-management](), [year-in-review]() ### AI overview Encore's 2023 year-in-review highlights product releases and engineering blog posts, including expanded secrets management, built-in application metrics, observability integrations, an API documentation Service Catalog, OpenAPI client generation, Pub/Sub improvements, and cloud infrastructure configuration. ### Source excerpt Our best new releases and engineering blogs in 2023 ## Results of Quick Testing of Documentation Tools' Accessibility DevFeed: [Results of Quick Testing of Documentation Tools' Accessibility]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:41.997000Z Content type: article Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Testing](), [Documentation](), [Swagger](), [Browser Extension](), [OpenAPI Specification](), [Document Object Model (DOM)]() Tags: [accessibility](), [automated](), [color](), [documentation](), [input](), [keyboard](), [openapi-specification](), [screen](), [swagger](), [testing]() ### AI overview This article reports quick accessibility testing of Swagger, Read the Docs, Docusaurus, and GitBook using the Axe browser extension, DOM inspection, and keyboard testing. The testing was not exhaustive because it did not include screen readers, narrower viewports, or zooming. For Swagger UI, Axe identified 64 issues, including color-contrast problems, form inputs without programmatically associated labels, and missing landmark regions. ### Source excerpt When writing my blog post about what backend devs can do for accessibility, I did some quick accessibility tests for different documentation tools. Initially, I thought I'd write about the results in that blog post, but there was just too much to report. So, I ended up writing this blog post. I chose four tools that I know many projects are using. These tools are: Swagger Read the Docs Docusaurus GitBook First, I ran an automated test with the aXe browser extension and dug deeper into the DOM based on the test results. After that, I tested the site with a keyboard. In this blog post, I'll share the test results and some thoughts about them. As you can see from the steps described above, the testing was not exhaustive. I just wanted to get an overview of the issues. I did not, for example, test with a screen reader or with narrower viewports (or zooming). This was a conscious decision, partly because I didn't have time and partly because this blog post would've been super long. And I think this already provides some overview of the state of accessibility of these tools. Let's get started. Swagger URL used for testing: https://petstore3.swagger.io/ Swagger is a set of tools used for API documentation. The Swagger API project started in 2011. Initially, it was a specification, but it was later named OpenAPI Specification. So it has a long history, and many projects use it. One of its tools is Swagger UI, a user interface for browsing the API endpoints. That's the one I'm testing for this blog post. Testing Swagger UI with Axe Runnin Axe-browser extension showed 64 issues, two of which are critical, 35 serious, 18 moderate, and 7 minor. Most of the issues (37) were related to color contrast issues. The contrast ratio for the problematic color combinations ranged between 2.03 and 3.75. Another problem was form input without programmatically associated labels. Some of them were flagged, but when I started digging deeper into the site's code, I noticed that not every insta ## Working with OpenAPI contract in multiple files DevFeed: [Working with OpenAPI contract in multiple files]() Original publisher: [Read original article]() Published: 2020-04-23T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [OpenAPI Specification](), [Swagger](), [API]() Tags: [api](), [code](), [download](), [editor](), [embedded](), [github-issues](), [openapi](), [openapi-specification](), [swagger]() ### AI overview This tutorial explains how to split a large OpenAPI specification into multiple files and work with external references. It discusses Swagger Editor's limitations, Stoplight Studio, swagger-ui-watcher, and a workflow for organizing a pet store API across separate files. ### Source excerpt Real-life OpenAPI specification files tend to go really big really fast. In this post, I'll try to explore how we can split single specification file into multiple files and don't get crazy while scrolling up and down like a mad man. Read more ## Creating a simple Kotlin Multiplatform project based on moko-template -- part 2 DevFeed: [Creating a simple Kotlin Multiplatform project based on moko-template -- part 2]() Original publisher: [Read original article]() Author: IceRock Development Published: 2019-11-17T12:05:17Z Content type: tutorial Language: en Sources: [Stories by IceRock Development on Medium]() Topics: [Kotlin Multiplatform](), [Template](), [OpenAPI Specification](), [API](), [Gradle](), [Library]() Tags: [android](), [gradle](), [ios](), [kotlin](), [kotlin-multiplatform](), [ktor](), [multiplatform](), [openapi-specification](), [project](), [serialization](), [software-development]() ### AI overview A tutorial showing how to build the second part of a GiphyApp series with Kotlin Multiplatform and the moko-template. It explains replacing a News API example with the GIPHY service by updating the OpenAPI specification, generated code, domain models, repository, and dependencies. ### Source excerpt Creating a simple Kotlin Multiplatform project based on moko-template -- part 21. Intro This manual is the second part in GiphyApp series, before you start we would recommend to do GiphyApp #1. The result of this lession is available on github. 2. Implement common logic of Gif list in shared library App should get list of Gifs from GIPHY service. There is an example with getting list of news from newsapi in the project template (using moko-network with generating network entites and API classes from OpenAPI specification). We can get OpenAPI spec of GIPHY from apis.guru and can replace getting news by getting Gif. Feature List is already in the project template and you have not to implement any additional logic. You can see scheme of module and look into mpp-library:feature:list for detail information about it. Replace OpenAPI spec Replace file mpp-library/domain/src/openapi.yml by the content from OpenAPI spec of GIPHY service. After it please do Gradle Sync and as the result you will see some errors in the newsapi code. Let's update code by new API. You can find generated files here mpp-library/domain/build/generate-resources/main/src/main/kotlin Replace news by gifs in domain module You have to update the following classes after replacing OpenAPI spec in domain module: News should be replaced by Gif; NewsRepository - should be replaced by GifRepository; DomainFactory - add gifRepository and set necessary dependencies. News -> Gif Let's modify News class to the following one: @Parcelize data class Gif( val id: Int, val previewUrl: String, val sourceUrl: String ) : Parcelable This domain entity contains gif's id and two URL (full and preview variant). id is used for correct identifying element in a list and in UI animations. Let's transform network entity dev.icerock.moko.network.generated.models.Gif to domain entity. To do this add one more construct method: @Parcelize data class Gif( ... ) : Parcelable { internal constructor(entity: dev.icerock.moko.network.genera ## Obtaining a URL to a file in a GitHub repository in a Travis CI build DevFeed: [Obtaining a URL to a file in a GitHub repository in a Travis CI build]() Original publisher: [Read original article]() Published: 2019-01-24T22:51:37Z Content type: tutorial Language: en Sources: [Miro Cupak]() Topics: [ci](), [GitHub](), [pull-requests](), [OpenAPI Specification](), [Swagger]() Tags: [ci](), [continuous-integration](), [devops](), [github](), [open-source](), [openapi-specification](), [pull-requests](), [swagger](), [travis](), [travis-ci]() ### AI overview A tutorial explaining how to construct a URL to a repository file in a Travis CI build while accounting for push builds, pull requests from forks, branches, and tags. ### Source excerpt I'm a fan of Travis CI and use it for continuous integration across pretty much all my open-source projects on GitHub. From time to time, I need to obtain a URL to a file in the repository in my build, e.g. to point a particular tool to it, in a way that respects branches as well as pull requests... ## What's new in version 2.5.0 of our client SDKs. DevFeed: [What's new in version 2.5.0 of our client SDKs.]() Original publisher: [Read original article]() Author: Tristan Sokol Published: 2017-11-15T22:11:37Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [SDKs](), [Transactions](), [OpenAPI Specification](), [API]() Tags: [api](), [apis](), [ci](), [developers](), [new-features](), [openapi](), [openapi-specification](), [release](), [sdks](), [transactions](), [travis-ci]() ### AI overview Square announces version 2.5.0 of its client SDKs, adding multi-party transactions, improving SDK generation instructions, removing the Travis CI SDK build pipeline, and fixing minor spelling issues. ### Source excerpt The latest version of our SDKs includes our big release of multi-party transactions.