> For the complete documentation index, see [llms.txt](https://docs.partssource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.partssource.com/api/resources/changelog.md).

# Changelog

API version history and release notes

This document tracks all notable changes to the PartsSource APIs.

***

## Versioning Policy

* **Current Version:** 1.0
* **Version Header:** `X-Api-Version: 1.0`

### Deprecation Policy

| Timeline  | Action                                          |
| --------- | ----------------------------------------------- |
| 6 months  | Advance notice before deprecating endpoints     |
| 12 months | Support period after deprecation announcement   |
| -         | Deprecation notices via email and documentation |

***

## Version 1.0

**Release Date:** October 2025

### Initial Release

The initial release of the PartsSource CustomerApi includes:

#### Authentication

* JWT Bearer token authentication via OAuth 2.0
* OAuth 2.0 Client Credentials flow for M2M integration
* 1-hour token expiration

#### Customer Management

* Customer lookup by ID or username
* Customer search with filters and pagination
* Company information retrieval with addresses and contacts

#### Catalog

* Catalog search with text queries and facet filtering
* Product detail retrieval with pricing options
* Support for multiple conditions (New, Refurbished, Exchange)

#### Orders

* Order creation with idempotency support
* Order retrieval by ID
* Quote items with custom fields

#### Core Features

* Offset-based pagination (up to 10,000 records per page)
* Idempotency for order creation (24-hour cache)
* Rate limiting (1,000 RPS standard tier)
* Correlation IDs for request tracking
* RFC 7807 Problem Details error responses

#### Multi-Tenancy (CustomerApi)

* Automatic tenant isolation based on client credentials
* Company-scoped data access
* No cross-tenant access permitted

#### Health Monitoring

* Liveness probe (`/health/live`)
* Readiness probe (`/health/ready`) with DB2 connectivity check

#### Documentation

* OpenAPI 3.0.1 specifications
* Interactive API documentation

#### Webhooks (2026-08)

* Webhooks documentation moved to its own section with Current and Preview variants

***

## Upcoming Changes

{% hint style="info" %}
The following features are planned for future releases. Dates are tentative and subject to change.
{% endhint %}

### Planned Features

| Feature              | Target | Status     |
| -------------------- | ------ | ---------- |
| Order status updates | TBD    | Planning   |
| Batch operations     | TBD    | Evaluation |

***

## Migration Guides

No migrations are currently required. This section will be updated when breaking changes are introduced in future versions.

***

## Support

For questions about API changes:

* **Email:** <api-support@partssource.com>
* **Include:** Correlation ID, environment, and affected endpoints


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.partssource.com/api/resources/changelog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.