Cliff DevChangelogs

Shuttle API - Changelog

1.0.0

First public release.

  • Every request type — HTTP, GraphQL with live subscriptions, WebSocket, Socket.IO, Server-Sent Events, gRPC from your .proto files or the server's own description, MQTT 3.1 to 5.0, and MCP, each with a panel of its own.
  • MCP servers — Fetch a server's tools, resources and prompts, browse and filter them in its catalogue, and call one with its arguments.
  • Each request keeps its response — Open another request and you see its own last result. A stream left connected keeps filling its log while you work elsewhere.
  • Authentication for the awkward cases — Bearer, Basic, Digest, API keys, OAuth 2.0 with all five grant types and PKCE, AWS Signature v4, OAuth 1.0, Hawk, NTLM, Akamai EdgeGrid, and client certificates per host.
  • Variables you can trust — Global, collection, environment and folder scopes, with a variable nothing defines struck through before you send. Write {{?code}} and Shuttle asks for the value as the request goes out.
  • Secrets stay secret — Secret values are kept in the Keychain and left out of every export, or read from HashiCorp Vault, AWS, Azure or Google Cloud when you send.
  • An assistant, if you want one — Ask Claude, OpenAI's models, or your own Ollama or LM Studio to write requests, tests and docs, send them and run folders. Every change waits for you to tap Allow, and it stays off until you choose a provider.
  • Why the assistant asks — A card that must always ask, such as a script or a send to a new address, says why instead of offering Allow all in this conversation.
  • Your secrets stay out of it — Secret values never reach the model, nor do tokens and passwords nobody marked secret, and your API key stays in the Keychain.
  • Code suggestions — Turn them on and the model suggests the rest of a script as you type. Tab takes it.
  • Scripts and tests — Pre-request and post-response scripts in JavaScript, with test() and expect(), fetch, CryptoJS, and a Visualize tab that shows a response as a table or a chart.
  • Postman, Bruno and Insomnia scripts run as written — An imported collection's tests and scripts work without being rewritten.
  • Run a folder or a whole collection — In order, with values carried from one request to the next, iterations, a data file and a delay. gRPC, MCP and streams run too, and the results save as JSON, JUnit or an HTML report.
  • See what you sent — A Wire tab shows the whole exchange, credentials masked, and a click on the time breaks it down, step by step.
  • History and comparison — Every send is kept and can be sent again, with the last 30 response times as a chart. Compare any two responses, saved examples or past sends.
  • Folders inside folders — Up to eight levels deep, each handing its auth, headers, variables and scripts down to what it holds.
  • Find anything [macOS] — Search inside requests, not only their names, open any action from the command palette, and rebind every shortcut.
  • Nothing is lost — Deleted requests and folders wait in the Trash, and Collection History takes a collection back to any earlier point.
  • Bring what you already have — Import from Postman, Insomnia, Bruno, Thunder Client, HAR, .http and .env files, and OpenAPI or Swagger, folders and settings included. Export any request as code in 27 forms, from cURL to Swift.
  • Collections in Git — Link a collection to a repository on GitHub, GitLab or any Git host: one readable file per request, synced on its own and merged part by part, with secrets kept out.
  • Git by hand — Commit, pull and push, with history, branches, stashes and pull requests, as in a Git client. The assistant can commit and merge for you too.
  • Work from your OpenAPI document — Preview it, lint it against 36 rules, compare it with a folder to find what is missing, and check every response against it. Try any operation straight from the document.
  • Write specs and docs — Turn a folder into an OpenAPI 3.0 or 3.1 document, or into Markdown or HTML documentation. Saved specs keep every version.
  • A mock server in the app — Load an OpenAPI document or write routes yourself, pick a port, and Shuttle answers every path, with realistic data where the document gives no example.
  • Mocks that behave like servers — Answer with any status, choose by rules on the request, remember what was posted, play back a recorded server, or add delays and failures on purpose.
  • Your own iCloud — Collections, environments and history sync through your iCloud account. Passwords, tokens and certificates stay on the device you entered them on.
  • Made for iPhone, iPad and iPhone Duo [iOS] — The request and its response stack, sized for the screen, with your collections beside them on iPad and on iPhone Duo unfolded.
  • Below or beside [macOS] — Put the response under the request or next to it.
  • In your language — Available in 21 languages, with a welcome tour and a searchable user manual in each.
  • Accessible — Works with VoiceOver, Increase Contrast and Reduce Motion throughout.
  • Built to survive a bad server — A response that never ends stops at 64 MB, a broken packet is skipped, and a server can only set cookies for itself.
  • Private by design — No account, no analytics, no server of ours: Shuttle talks only to the servers you point it at.