> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/apptivo/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>Invalid API key error when connecting</summary>

Double-check that you've copied the full API key from Apptivo without any leading or trailing spaces. In Apptivo, go to **Settings → API & Webhooks → API Key** to view or regenerate your key. If you recently regenerated a key, the old one is immediately invalidated — update Coupler.io with the new value.

</details>

<details>

<summary>Data flow fails immediately after setup</summary>

This can happen if your Apptivo user account doesn't have API access enabled. API access may need to be turned on at the plan or admin level. Check with your Apptivo administrator to confirm that API access is active for your account.

</details>

## Missing data

<details>

<summary>Some records are missing from the export</summary>

Apptivo's API only returns active, non-deleted records. If a customer, lead, or case was deleted in Apptivo, it won't appear in Coupler.io. Also check whether the records are assigned to a different user — depending on your Apptivo permissions, you may only see records you own or have access to.

</details>

<details>

<summary>Custom fields are not appearing in the output</summary>

Custom fields are included in the export, but their column names will match the labels set in your Apptivo account. If a custom field was recently added in Apptivo, try running the data flow again — Coupler.io will pick up new fields on the next run.

</details>

## Permission errors

<details>

<summary>403 Forbidden or "Access denied" error</summary>

This typically means the API key belongs to a user who doesn't have read access to the entity you're trying to export. For example, if your user role restricts access to Opportunities, the API will return a 403. Ask your Apptivo admin to adjust permissions for that user, or use an API key from an admin account.

</details>

## Data discrepancies

<details>

<summary>Record counts in Coupler.io don't match Apptivo</summary>

Apptivo's UI counts may include archived or filtered records that the API excludes. Specifically, the API typically excludes deleted records and may apply default filters (e.g., only returning records in an "active" status). Compare with an unfiltered Apptivo list view rather than a saved filtered view.

</details>

<details>

<summary>Field values look different from what I see in Apptivo</summary>

Some Apptivo fields store an internal ID or code rather than the display label. For example, a status field might export as a numeric code instead of "Closed Won". This is an Apptivo API behavior. You can use a lookup table or Coupler.io's transformation features to map these codes to readable labels.

</details>

## Rate limits

<details>

<summary>Data flow is slow or times out on large entities</summary>

Apptivo enforces API rate limits that vary by plan. If you have a large number of records (thousands of leads or cases), the export may take longer as Coupler.io pages through the results. Avoid running multiple data flows against Apptivo simultaneously to reduce the chance of hitting rate limits.

</details>


---

# 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.coupler.io/sources/category/crm/apptivo/common-issues.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.