Moving from Paw on macOS 27?
Nokia says on paw.cloud that “upcoming macOS releases, including macOS 27, will not be tested, certified, or officially supported by Nokia.” Saluki imports your .paw files directly, so your requests don't have to start over.
The beta opens soon.
Import your .paw file
On Mac, choose File → Import… and pick your .paw file, or drag it straight onto the Saluki window. On iPhone and iPad, Import opens a file picker. No export step, and Paw doesn't need to be installed.
What comes across
- Requests, folders, headers and query parameters
- Bodies: text, JSON, form and multipart
- Request notes and environments
- Request variables and response chaining
- Basic Auth typed into the request
- Redirect, cookie and timeout settings
When you import, literal tokens and passwords in Paw's Authorization headers, and in common API key headers such as X-API-Key, go to your Keychain instead of your files. Limits:
- A Paw request variable used that way stays in its file, with a warning.
- A copy of the same value in a body, a URL or another variable stays as the .paw had it, with a warning.
- Tokens in custom headers that aren't a known API-key name stay in the file, so check those.
What doesn't come across
The main gaps:
- OAuth 1 and 2, and AWS Signature v4
- JavaScript dynamic values and Paw extensions
- GraphQL, gRPC and MessagePack bodies
- Hash, HMAC and similar dynamic values
- Client certificates
- Paw's tests
- Values Paw kept in the Keychain or encrypted — you re-enter these by hand
- Paw's own request order
- Timestamps in other formats and random strings (approximated)
- Request- and response-derived values such as Base64
Response history and cookies: Paw 2 and later keep them outside the .paw file, so they can't come across.
Paw → Saluki
| In Paw | In Saluki |
|---|---|
| Groups | Folders |
| Environment domains | http-client.env.json |
| Response body key path | {{name.response.body.$.path}} |
| Secure values | Keychain secrets. Values Paw kept in its Keychain or encrypted are re-entered by hand. |
| Code generators | Copy as: curl, Swift, JavaScript, Python or .http (five targets) |
| Team sync | Saluki has no sync of its own. Your requests are plain files: use git or any synced folder. |
Why plain files
A .http file isn't a Saluki format. It's the format JetBrains IDEs and Visual Studio 2022 (17.8+) open, and VS Code with the REST Client extension. Commit it, diff it, open it in another editor.
Other options
Saluki isn't the only way forward. Stated plainly, so you can pick:
- Keep Paw on your current macOS for now. Nokia says on paw.cloud that “PAW continues to operate on currently supported macOS versions.”
- Export from Paw. Paw, in its own words, can “generate client code and export API definitions” — Swagger and RAML among them — for any tool that reads them.
- HTTPBot is an API client for Mac, iPhone and iPad, available on the App Store.
- Postman is a cross-platform API platform, used as a desktop app or in the browser.
- Bruno is an open-source, cross-platform API client that stores collections as plain-text files in your repo.
- Yaak is a local-first, open-source API client for Mac, Windows and Linux, built with Rust and Tauri.
Price and privacy
- Free
- 1 collection
- Pro
- $19.99 until Nov 8, then $29.99
One purchase unlocks Mac, iPhone and iPad. No account, no analytics, no data collected.
Read the full Saluki page and the privacy policy.
FAQ
Which macOS does it need?
macOS 26 or later. It's built and tested on macOS 27.
Does it need an account?
No. There's no account and no sign-in, on any platform.
My team uses JetBrains: does that work?
Partly. Imported requests are .http files, but three things differ: response chaining isn't JetBrains syntax; JetBrains doesn't expand {{…}} inside environment values; and values saved in your Keychain are empty to other tools.
What about scripts?
Saluki doesn't run scripts, including Paw's JavaScript dynamic values. The import report flags what Saluki can't convert, such as OAuth, JavaScript values and Paw extensions.
Try it
The beta opens soon.