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

# 1Password partner quickstart

> Integrate 1Password as a partner: billing with the Partnership API, user lifecycle with the Users API, and the Save in 1Password button for your website.

1Password partners are third-party organizations who integrate 1Password into their products or services to manage things like account billing, user lifecycle automation, and website autofill integration.

<Tip>
  Learn how to join the [1Password Partner Program](https://1password.com/partners).
</Tip>

## Choose your path

Start with the use case that matches your needs:

<CardGroup cols={3}>
  <Card title="Billing integration" href="#billing-integration" icon="handshake">
    Provision and manage billing for individual and family accounts.
  </Card>

  <Card title="User automation" href="#user-automation" icon="users">
    Automate access control and user lifecycle for enterprise accounts.
  </Card>

  <Card title="Web experience" href="#web-experience" icon="browser">
    Let users save sign-in details and improve autofill on your site.
  </Card>
</CardGroup>

## Billing integration

Use the [1Password Partnership API](/partnership-api/reference/) to manage partner billing accounts for individual and family plans.

<Tip>
  Integrating 1Password account billing with third-party products and services is only available to registered partners. To request access, visit the [1Password Partner Program](https://1password.com/partners) or [contact the Partnerships team](mailto:partners@1password.com).
</Tip>

Typical flow:

1. Authenticate using your partner-issued bearer token.
2. Create a billing account for a customer.
3. Generate a partner billing link using the activation token.
4. Manage the customer's account lifecycle (retrieve the account status, update the billing end date, or delete the account).

<Card title="Partnership API reference" href="/partnership-api/reference" icon="file-lines">
  Endpoints, request formats, and billing link details.
</Card>

## User automation

Use the [1Password Users API](/users-api/) to automate access control and user lifecycle management for enterprise accounts as part of SOC or SIEM workflows.

Typical flow:

1. Create an OAuth application in 1Password.
2. Request an access token using client credentials.
3. Call user endpoints (list, suspend, reactivate).

<CardGroup cols={2}>
  <Card title="Get started with the 1Password Users API" href="/users-api/get-started" icon="key" />

  <Card title="Users API reference" href="/users-api/reference" icon="book" />
</CardGroup>

## Web experience

### Save in 1Password button

Use the [Save in 1Password button](/web/add-1password-button-website) to allow visitors to your website to save sign-in details, credit cards, crypto wallets, or API keys (if you register as a partner) to their 1Password account in one step.

1. Install the [`@1password/save-button`](https://www.npmjs.com/package/@1password/save-button) package and import it in your page.
2. Build a **save request** with the fields your item type needs.
3. Render the custom element with the required attributes so 1Password can offer to save when appropriate.

<Card title="Add the Save in 1Password button" href="/web/add-1password-button-website" icon="floppy-disk">
  Install the package, build save requests, and wire the button on your site.
</Card>

### Design webpages that work well with 1Password

Good form structure and semantics help the 1Password browser extension fill, save, and update passwords reliably. Follow [web best practices](/web/compatible-website-design): logical forms, correct `autocomplete` values, clear password-change flows, and optional `data-1p-ignore` where a field should be ignored.

<Card title="Design your website for 1Password" href="/web/compatible-website-design" icon="browser">
  Forms, password rules, passkeys, and patterns that improve filling and saving.
</Card>

## Next steps

Explore these guides when you are ready to go deeper on a specific integration path:

<CardGroup cols={2}>
  <Card title="Partnership API reference" href="/partnership-api/reference" icon="handshake">
    Full billing API details, environments, and customer link formats.
  </Card>

  <Card title="Users API overview" href="/users-api/" icon="users">
    Requirements, preview status, and links to authorization and endpoints.
  </Card>

  <Card title="Save in 1Password button" href="/web/add-1password-button-website" icon="floppy-disk">
    NPM package, save requests, and embedding the button.
  </Card>

  <Card title="Compatible website design" href="/web/compatible-website-design" icon="window">
    Make sign-in and account flows work smoothly with 1Password in the browser.
  </Card>
</CardGroup>


## Related topics

- [1Password Accounts API for Partners](/accounts-api.md)
- [1Password developer quickstart](/get-started/developer-quickstart.md)
- [Reference for the 1Password Accounts API for Partners](/accounts-api/reference.md)