> ## Documentation Index
> Fetch the complete documentation index at: https://docs.partfinder.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The PartFinder API is served at https://api.partfinder.dev. Authenticate with `Authorization: Bearer $PARTFINDER_API_KEY`; create an account at https://console.partfinder.dev/sign-up and pick pay as you go or a monthly or yearly plan (see https://partfinder.dev/pricing), then create a key. Pay as you go starts with 100 free credits, once per person and per company.
> Install the PartFinder agent skill with `npx skills add https://docs.partfinder.dev` (skill file: https://docs.partfinder.dev/skill.md).
> The OpenAPI document at https://api.partfinder.dev/v1/openapi.json is the source of truth for request and response schemas.
> What each call costs and current plans: https://api.partfinder.dev/llms.txt.

# PartFinder Console: Organization, Members and Roles

> How access to the PartFinder Console works: your organization, the Admin and Member roles, usage and the request log, webhooks, and inviting teammates.

The [PartFinder Console](https://console.partfinder.dev) is where your team manages its API keys and sees its usage. Creating, rotating and revoking keys is covered in [Authentication](https://docs.partfinder.dev/authentication.md); this page covers who can use the console and what each person can do.

## Access

Anyone can create an account at [console.partfinder.dev/sign-up](https://console.partfinder.dev/sign-up).

## Your organization

Your organization is your company in PartFinder. Your API keys belong to it rather than to any one person, so they keep working when someone joins or leaves. Your organization ID is shown on the **Organization** page and is returned as `authenticated.organization_id` by `GET /v1/ping`.

## Roles

| | Admin | Member |
| - | - | - |
| See the organization's API keys | Yes | Yes |
| Create an API key | Yes | Yes |
| Edit, rotate or revoke keys they created | Yes | Yes |
| Edit, rotate or revoke anyone's keys | Yes | No |
| See members | Yes | Yes |
| Invite and remove members, change roles | Yes | No |
| Rename the organization or change its logo | Yes | No |
| Delete the organization | Yes | No |
| Leave the organization | Yes | Yes |
| See usage and the request log | Yes, whole organization | Yes, keys they created |
| See webhook endpoints and deliveries | Yes, whole organization | Yes, keys they created |
| Set key and member limits, ask for a higher limit | Yes | No |

A key's secret is shown once, when it is created. Nobody can see it again afterward, whatever their role.

## Usage and request log

The **Usage** group in the console sidebar has three pages: **Overview**, **Request log** and **Limits**. Times are in UTC.

Every API call made with a valid key is recorded as one line: the time, the endpoint, the result (status code) and the key used. What you sent and what we returned are never recorded.

Your organization's admins see these lines in the console's **Request log** and can download them as a CSV file (**Download**: last 24 hours or last 7 days). Other members see only the lines for keys they created.

If you create keys for your own customers with `POST /v1/keys`, their calls appear in your **Request log** under those keys. Your customers have no console access.

**Overview** shows calls over time, errors, calls by endpoint and by key, and your busiest minute and day against your limit.

**Limits** shows your limit. An admin can set a lower limit for one key or one member (every key that member created) with **Edit limit**, and can ask for a higher limit with **Contact us about a higher limit**.

## Webhooks

The **Webhooks** page lists your webhook endpoints and the **Deliveries** sent to them. Times are in UTC.

For each endpoint you see its **URL**, the **Key** it was registered with, what it **Receives** and when it was **Registered**. **Receives** reads "All your organization's events" for an endpoint registered with one of your organization's own keys, or "One customer's events" for one registered with a key you created for a customer.

For each delivery you see the **Time**, the **Event**, the **Endpoint**, the **Status**, the number of **Attempts** and the **Last answer**. **Last answer** is the status code your server returned, or "No answer" when it did not answer.

| Status | Meaning |
| - | - |
| Delivered | Your server answered with a `2xx`. |
| Retrying | Your server has not accepted it yet. We will try again. |
| Failed | We stopped trying. Every attempt was used, or the retry period of about three days ended. |

Your organization's admins see every endpoint of the organization. Other members see the endpoints registered with keys they created, and the deliveries to those endpoints.

You register and remove endpoints with the API, see [Webhooks](https://docs.partfinder.dev/webhooks.md). The console never shows an endpoint's signing secret.

## Inviting a teammate

**1. Open the members list**

As an Admin, open **Organization** in the console and go to **Members**.

**2. Send the invitation**

Click **Invite**, enter your teammate's work email address, choose **Admin** or **Member**, and send. Pending invitations are listed under **Invitations**, where an Admin can revoke one.

**3. Your teammate accepts**

Your teammate opens the email, follows the link and creates their account. They land in the console as a member of your organization.

You can invite anyone by email address, whatever their company.

## Leaving an organization

Any member can leave from **Organization** → **General** → **Leave organization**. Leaving removes only your own membership; the organization's keys keep working.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.