Welcoming Clerk.com to the Speakeasy family! 🎉 Clerk has crafted the best DevEx for user management bar-none. We're honored to help them deepen their server-side DevEx with their new Python SDK 🐍 Read about it on the slickest changelog in existence 👇
Speakeasy
Software Development
San Francisco, California 2,658 followers
🐝 World-class Developer Experience for your API 🐝
About us
Building a best in class API supply chain. Robust SDKs, Terraform Providers and a toolkit to power quality REST API development at scale.
- Website
-
https://www.speakeasyapi.dev/
External link for Speakeasy
- Industry
- Software Development
- Company size
- 2-10 employees
- Headquarters
- San Francisco, California
- Type
- Privately Held
- Founded
- 2022
Locations
-
Primary
Get directions
San Francisco, California, US
Employees at Speakeasy
Updates
-
#OBExpo We are coming to the Open Banking Expo in London next week. Stop by the Speakeasy booth, and let's chat all about #API innovation: https://lnkd.in/eJZH6C6P
-
Speakeasy reposted this
Introducing the Dub.co CLI: dub.link/cli Easily shorten and manage your links directly from your terminal. Built by one of our amazing community contributors, Suraj, using the Dub TypeScript SDK.
-
Speakeasy reposted this
I was lucky enough to get a REALLY cool peek behind the curtain at this feature, and I am very excited to see Postman moving in this direction. Typed parameters, requests, and variables is going to be a GAME CHANGER for Postman collections. Personally, I still would have preferred alignment on a standard for documenting the APIs (like OpenAPI) but I appreciate that this level of typing detail is coming to the tool.
If you’ve used Postman before you know that one powerful but sometimes deceptively complex feature is variables. Sometimes it can be hard to tell: what’s the value of this variable? Or, where is it stored? Or, gosh, how the heck do I edit this dang thing just to get my request working? We at Postman don’t think you should have to care! So regardless of where your variable is scoped and stored (or not!) now with the launch of our new and improved variables experience: we let you edit in place in any of the five scopes your variable can be using to send a request (yes, there are five scopes!) or opt-out of any scope and set a local temporary variable to an individual request. These are the kinds of improvements we are making to Postman with each and every release. We aim to make the lives of developers building APIs easier, simpler, and faster. With this release, we not only closed the currently most requested feature in our issue tracker (https://lnkd.in/eCgxhW7z), but also twelve additional issues. Abhijit Kane described this release as "This is like the long red block in tetris that clears 4 rows at once." 😂 This kind of innovation to core workflows is not easy, but it’s very much worth doing and a responsibility we take seriously. It takes a village, so credit to numerous members of the API client team: Shobhit Katikia and Udit Vasu for the vision and relentless pursuit of polished experience to re-create the variables experience, Rohan Grover and Dev Sharma for their tireless efforts as builders to build, build, build and take the team's persistent nudges to keep polishing, and last but certainly not least Giridhar V.C for his critique and feedback and driving the team forward with urgency. Don’t just take my word for it though, download the latest version of Postman today (or see below for a quick visual example) to take it for a spin. Let us know what you think, and how we can keep improving the Postman experience for you: the developer. Our job’s not finished, and we have so much more to build. https://lnkd.in/eSF2Tt9E
-
-
With the world full of ever more sophisticated attackers, Prove is on a mission to modernize digital trust and make it easy for businesses to conduct accurate identity verification. And to make it as easy as possible for developers to integrate Prove into their applications, they’re using Speakeasy to create SDKs in a range of popular languages. Head over to Github to try them out: https://lnkd.in/eM2XrS24
-
-
Great name, great domain, great tool. Its got it all ! #zod
Today I'm shipping https://zod.fyi We codegen TypeScript SDKs from OpenAPI for our customers at Speakeasy and Zod (https://zod.dev) is a critical building block that we chose to power runtime validation. Depending on the complexity of a Zod schema, the resulting validation error message can contain a wall of JSON text - the serialised issues that were recorded during validation. I wanted to try and create a small tool to help me better visualise and parse these errors. In code and the command line, we do also have the ability to pretty-print the errors but I still wanted a web UI which can let me share URLs for visualised errors. I'm still iterating on it but would love any feedback if you do get to try it out.
What in Zod's name?
zod.fyi
-
We love great SDKs, whether they're built by us, or other people. Which is why we're sponsoring Drew Powers' TypeScript generator. Thousands of developers at companies both big and small have been using Drew's tooling for years. We're happy to be doing our small part to make sure that it remains maintained and available to the public to use.
-
-
The continued progress of localized AI applications depends on companies being able to make all of their data available to LLM models. Fortunately, Ragie is making it easy with a fully-managed RAGaaS offering 🤖 And we're delighted to be supporting the development of their Python & TypeScript SDKs to make the integration process as easy as possible. If you're building an AI application and need to access your data, check out Ragie.ai! https://lnkd.in/gETMA9xn
-
-
We're excited to announce that we're sponsoring the encode.io team's HTTPX project! 🎉 They’re pushing the Python ecosystem 🐍 forward with the best HTTP client available, making it easy to build for sync & async use cases. We hope others will join us in supporting the team's work! Our Python SDK generation wraps HTTPX to enable users to send both sync & async requests from a single client. It wouldn't have been possible to build without the foundation built by the Encode team. If you want a deep dive on the different HTTP clients in the Python ecosystem, and why we think HTTPX is the best for most use cases, we wrote about our design decision here: https://lnkd.in/e-nuHXY2
-