> 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/getting-started/readme.md).

# API Documentation

Complete guide to the PartsSource Customer API

The PartsSource APIs follow RESTful design principles with resource-oriented URLs, JSON request/response bodies, and standard HTTP methods.

## Quick Links

| Section                                                                              | Description                     |
| ------------------------------------------------------------------------------------ | ------------------------------- |
| [Getting Started](/getting-started/getting-started/making-your-first-api-request.md) | Make your first API request     |
| [Authentication](/getting-started/authentication/overview.md)                        | OAuth 2.0 authentication flow   |
| [Core Concepts](/getting-started/core-concepts/error-handling.md)                    | Idempotency, pagination, errors |

***

## Getting Started

New to the PartsSource APIs? Start here:

1. [**Request API credentials**](/getting-started/authentication/requesting-oauth-2.0-client.md) - Get your client ID and secret
2. [**Authenticate**](/getting-started/authentication/overview.md) - Obtain an access token
3. [**Make your first request**](/getting-started/getting-started/making-your-first-api-request.md) - Call an endpoint

***

## Core Concepts

Before building your integration, understand these fundamentals:

* [**Error Handling**](/getting-started/core-concepts/error-handling.md) - Response formats and status codes
* [**Idempotency**](/getting-started/core-concepts/idempotency.md) - Prevent duplicate operations
* [**Pagination**](/getting-started/core-concepts/pagination.md) - Navigate large result sets
* [**Rate Limiting**](/getting-started/core-concepts/rate-limiting.md) - Stay within API limits
* [**Correlation IDs**](/getting-started/core-concepts/correlation-ids.md) - Debug requests with support

***

## Need Help?

* [**Troubleshooting**](/getting-started/resources/troubleshooting.md) - Common issues and solutions
* [**Status Codes**](/getting-started/resources/http-status-error-codes.md) - HTTP error reference
* **Support:** <api-support@partssource.com> (include the `correlationId` from your request)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.partssource.com/getting-started/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.