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

# API Access Token

> Connect Parable to Zephyr Cloud using an API access token

export const platform_0 = undefined

export const limit_0 = undefined

export const tokenName_0 = undefined

<Tabs>
  <Tab title="Setup">
    <Card title="What You'll Need" icon="key">
      | Credential           | What it is                                                                    |
      | -------------------- | ----------------------------------------------------------------------------- |
      | **API Access Token** | A token generated from your Jira Cloud profile under Zephyr API Access Tokens |
    </Card>

    ## Overview

    Connect Parable to Zephyr Cloud using a single API access token. Parable ingests test cases, test cycles, execution results, and step-level data across all Jira projects accessible to the token.

    <CardGroup cols={2}>
      <Card title="Test execution data" icon="check">
        Test cycles, executions, and step-level results
      </Card>

      <Card title="Test definition data" icon="list">
        Test cases and their step definitions
      </Card>
    </CardGroup>

    ## Prerequisites

    * A **Jira Cloud account** with **Zephyr Cloud** (or Zephyr Cloud) installed.
    * Your account must have permission to access test data in at least one Jira project.

    ## Setup Guide

    <Steps>
      <Step title="Open Zephyr API Access Tokens">
        1. Sign in to Jira Cloud.
        2. Click your **profile icon** in the top-right corner.
        3. Select **Zephyr API Access Tokens** from the dropdown menu.

        <Tip>
          You can also navigate directly to your Jira Cloud instance and look for "Zephyr API Access Tokens" in your profile menu.
        </Tip>
      </Step>

      <Step title="Create a new access token">
        1. Click **Create access token**.
        2. Give the token a descriptive name (e.g. "Parable integration").
        3. Copy the generated token immediately.

        <Warning>
          **Copy your {tokenName_0} now!**

          This is the only time it will be displayed. Store it in a secure password manager before closing this page.
        </Warning>

        <Warning>
          The token is shown only once at creation time. If you navigate away without copying it, you must create a new token.
        </Warning>
      </Step>

      <Step title="Connect in Parable">
        1. In Parable, open **Settings > Connectors > Add connector**.
        2. Select **Zephyr Cloud**.
        3. Paste your **API Access Token**.
        4. Click **Save & verify**.

        <Check>
          **Success!** If you received a `200 OK` response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.
        </Check>
      </Step>
    </Steps>

    <Tip>
      **Rate Limits:** {platform_0} enforces rate limits of **{limit_0}**.

      Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
    </Tip>
  </Tab>

  <Tab title="Troubleshooting">
    ## Common Issues

    **Validation fails immediately after entering the token**

    * Confirm you copied the full token without leading or trailing whitespace.
    * The token may have been revoked. Return to the Zephyr API Access Tokens page and create a new one.
    * Ensure your Jira account has access to at least one project with Zephyr Cloud data.

    **Some projects show no data**

    * Zephyr access is scoped to Jira project permissions. The account that generated the token must have at least **Browse Projects** permission in every project you want to ingest.

    **Rate limit errors during initial sync**

    * Zephyr Cloud enforces rate limits per token. Parable automatically respects retry delays. A large initial sync across many projects may take longer than expected -- no action required.

    **`testcases` or `testcycles` tap returns empty results**

    * Confirm that test cases and cycles exist in your Jira projects. If no test data has been created in Zephyr Cloud, the taps will return no records.
  </Tab>
</Tabs>