# Parse-Swift minimum Parse Server version?

**URL:** <https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419>\
**Category:** ParseSwift SDK\
**Created:** [February 10, 2022, 4:15pm UTC](https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419 "2022-02-10T16:15:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![claesjacobsson](https://community.parseplatform.org/letter_avatar_proxy/v4/letter/c/2bfe46/32.png) [@claesjacobsson](https://community.parseplatform.org/u/claesjacobsson)\
**Post date:** [February 10, 2022, 4:15pm UTC](https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/1 "2022-02-10T16:15:29Z")

</div>

Is there a compatibility matrix for Parse-Swift and Parse server versions?

---

<div class="post-metadata">

**Author:** ![cbaker6](https://community.parseplatform.org/user_avatar/community.parseplatform.org/cbaker6/32/114_2.png) [@cbaker6](https://community.parseplatform.org/u/cbaker6)\
**Post date:** [February 10, 2022, 10:17pm UTC](https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/2 "2022-02-10T22:17:41Z")

</div>

No table available at the moment, but it uses the [REST API](https://docs.parseplatform.org/rest/guide/), so it essentially should be backwards compatible with most server versions. The older the version, the less features the server will have along with the possibility of bugs that are fixed in newer versions. The [documentation](http://parseplatform.org/Parse-Swift/api/) will let you know if a particular feature in ParseSwift requires a server minimum version.

Note that this is the case with any of the [Parse Client SDK’s](https://parseplatform.org/#sdks). The only difference is the Swift SDK is currently kept up-to-date with the latest Parse Server features while some of the other SDK’s may be behind in features.

I’ve personally tested some of the [Playground code](https://github.com/parse-community/Parse-Swift/tree/main/ParseSwift.playground/Pages) on Parse Server 4.2 and most seemed to work from what I could see…

---

<div class="post-metadata">

**Author:** ![claesjacobsson](https://community.parseplatform.org/letter_avatar_proxy/v4/letter/c/2bfe46/32.png) [@claesjacobsson](https://community.parseplatform.org/u/claesjacobsson)\
**Post date:** [February 10, 2022, 10:36pm UTC](https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/3 "2022-02-10T22:36:46Z")

</div>

Thanks! Currently running an app on Sashido which only supports up to 3.6.0 at the moment. But I’ll do some testing 🙂

---

<div class="post-metadata">

**Author:** ![cbaker6](https://community.parseplatform.org/user_avatar/community.parseplatform.org/cbaker6/32/114_2.png) [@cbaker6](https://community.parseplatform.org/u/cbaker6)\
**Post date:** [February 11, 2022, 1:35am UTC](https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/4 "2022-02-11T01:35:56Z")

</div>

I suspect the earliest version that might work with ParseSwift is:

> **[Release 2.6.4 · parse-community/parse-server](https://github.com/parse-community/parse-server/releases/tag/2.6.4)**
>
> 2.6.4
> Full Changelog
> Improvements:
> 
> Improves management of configurations and default values, thanks to Florent Vilmart
> Adds ability to start ParseServer with ParseServer.start(options), thanks to ...

This due to logging in via `POST`. The Swift SDK uses `POST` instead of `GET` for most REST calls. So if an old version doesn’t support `POST` in place of `GET`, you will most likely will run into trouble. Of course, there’s also the bug fixes and missing features, so I wouldn’t expect everything to work, but my guess is it still supports more features than the Objective-C SDK.

POST calls:

[https://github.com/parse-community/Parse-Swift/search?q=.POST](https://github.com/parse-community/Parse-Swift/search?q=.POST)