> 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/authentication/requesting-oauth-2.0-client.md).

# Requesting API Access

How to request API credentials for PartsSource APIs

To use the PartsSource APIs, you need OAuth 2.0 client credentials. This guide explains how to request access and what to expect.

***

## What You'll Receive

After approval, you'll receive:

| Credential        | Description                          | Keep Secret?                    |
| ----------------- | ------------------------------------ | ------------------------------- |
| **Client ID**     | Your application's unique identifier | No (but don't share publicly)   |
| **Client Secret** | Your application's secret key        | **Yes - treat like a password** |
| **API Key**       | Your API key (`x-api-key` header)    | **Yes - treat like a password** |

***

## Prerequisites

Before requesting access, ensure you have:

* [ ] A valid business relationship with PartsSource
* [ ] A clear use case for API integration
* [ ] Technical contact information

***

## Request Process

{% stepper %}
{% step %}

#### Contact Your Account Manager

Reach out to your PartsSource account manager or contact <api-support@partssource.com> to initiate the API access request.

Include in your request:

* Company name and account information
* Integration use case description
* Technical contact name and email
* Preferred environment(s): Production, QA, or both
  {% endstep %}

{% step %}

#### Review and Approval

Our team will review your request and may ask clarifying questions about:

* Intended data usage
* Security measures in place
* Integration architecture

**Typical review time:** 5-10 business days
{% endstep %}

{% step %}

#### Receive Credentials

Upon approval, you'll receive your credentials via secure channel:

* Client ID and Client Secret
* Environment-specific endpoints
* Any usage guidelines or restrictions

{% hint style="warning" %}
**Store your client secret securely.** It cannot be recovered if lost - you'll need to request new credentials.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## Environment Access

You can request access to different environments:

| Environment    | Purpose                 | Typical Access      |
| -------------- | ----------------------- | ------------------- |
| **QA**         | Testing and development | Granted first       |
| **Production** | Live integration        | After QA validation |

{% hint style="info" %}
**Recommended approach:** Start with QA access, validate your integration, then request production credentials.
{% endhint %}

***

## Security Requirements

To maintain API access, you must:

### Credential Security

* Store credentials in secure secret management systems
* Never commit credentials to source control
* Rotate credentials if compromise is suspected
* Use separate credentials for each environment

### Integration Security

* Use HTTPS for all API communication
* Implement proper error handling
* Follow rate limiting guidelines
* Log correlation IDs for debugging

### Compliance

* Only access data your integration requires
* Comply with data handling agreements
* Report any security incidents promptly

***

## Credential Rotation

If you need to rotate credentials (suspected compromise, security policy, etc.):

1. Contact <api-support@partssource.com>
2. Request new credentials
3. Update your integration with new credentials
4. Confirm old credentials should be revoked

{% hint style="danger" %}
**Credential revocation is immediate.** Ensure your integration is updated before requesting revocation of old credentials.
{% endhint %}

***

## Multiple Integrations

If you have multiple applications or services that need API access:

| Approach                 | When to Use                          |
| ------------------------ | ------------------------------------ |
| **Shared credentials**   | Same application, multiple instances |
| **Separate credentials** | Different applications or teams      |

**Recommendation:** Use separate credentials for each distinct integration to:

* Isolate access if one is compromised
* Track usage per integration
* Apply different rate limits if needed

***

## Support

For questions about API access:

| Topic               | Contact                       |
| ------------------- | ----------------------------- |
| New access requests | Your account manager          |
| Technical issues    | <api-support@partssource.com> |
| Credential problems | <api-support@partssource.com> |
| Security concerns   | <security@partssource.com>    |

When contacting support, include:

* Your company name
* Client ID (not secret!)
* Environment (QA/Production)
* Description of issue or 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 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/authentication/requesting-oauth-2.0-client.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.