> For the complete documentation index, see [llms.txt](https://guide.fariaedu.com/integrations-portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.fariaedu.com/integrations-portal/managebac/public-rest-apis/about-versions.md).

# About Versioning

### Introducing Versioning for ManageBac+ Public REST APIs.

Up until May 2025, the ManageBac+ Public REST APIs only had one version: `v2` . Previously, the `v2` version was considered stable and deprecations were introduced gradually. **Starting July 2025**, we introduced **v2pX** versions, enabling us to iterate on the "latest" `v2` more frequently.

Whenever ManageBac+ introduces a breaking change to the public API, the version `v2` will inherit the change, and a new version `v2pX` will inherit the breaking changes. Any subsequent non-breaking changes will be inherited in `v2` and `v2pX`, until another breaking change is introduced. At that point, `v2pY` version will inherit the new breaking change, as well as `v2`. 

We've established the following structure to help integration partners evaluate which version best meets their needs. 

| Version | Description                                                                                                                        | Suggested Use                                                                                                                                             |
| ------- | ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `v2`    | New endpoints, additional fields, and breaking changes can be introduced.                                                          | Suitable for integrations that prioritize having latest updates. Not suitable for mission-critical integrations.                                          |
| `v2p0`  | This version incorporates all functionality prior to April 2025. Stable until further notice.                                      | Suitable for legacy integrations that guarantees legacy behavior. Will be deprecated when `v2p3` is introduced.                                           |
| `v2p1`  | This version deprecates supporting updating `child_ids` in `PATCH /students/{id}`                                                  | Suitable for new integrations that use features introduced after April 2025, but also guarantees stability. Will be deprecated when `v2p4` is introduced. |
| `v2p2`  | This version has a breaking change in the task data model. The response in "Get all Tasks" and "Get a Task" has been restructured. | Suitable for new integrations that prioritize stability. Will be deprecated when `v2p5` is introduced.                                                    |

### Implementation

After determining the best approach for your integration, please adjust the path of the baseUrl used in integrations.

For example, if you elect to use `v2p0` , which has the same functionality from April 2025 and will remain stable until further notice, instead of calling:

```
https://api.managebac.com/v2/students
```

Instead, use: 

```
https://api.managebac.com/v2p0/students
```