> 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/finance-and-accounting/concord/common-issues.md).
# Common Issues
## Connection issues
My API key is rejected and the data flow won't connect
Double-check that you've copied the full API key from Concord — partial keys are a common cause. You can find your API key under **Settings > API** in your Concord account. Also confirm that API access is enabled for your account tier; some Concord plans restrict API usage.
The data flow fails immediately after setup
This usually points to a connectivity issue between Coupler.io and the Concord API. Try re-entering your API key in the source settings to rule out a copy-paste error. If the problem persists, check Concord's status page for any active incidents.
## Missing data
Some agreements aren't showing up in my export
Concord's API only returns records that your API key's account has permission to access. If agreements belong to a different organization or folder that your account can't read, they'll be silently excluded. Check whether the missing agreements are in a restricted folder or owned by another org.
The Reports entity returns no data or very few rows
The Reports entity returns Concord's pre-built reports, which must exist in your account before they appear here. If you haven't created any reports inside Concord, this entity will be empty. Create or save a report in Concord first, then re-run the data flow.
Tags or folder associations are missing from agreements
Tags and folder data are separate entities that link to agreements by ID. If you're looking for this data in the Agreements entity alone, it will appear as IDs rather than names. Pull the Tags and Folders entities separately and use a Join transformation in Coupler.io to enrich your agreements with the full labels.
## Permission errors
I get a 403 or "insufficient permissions" error on certain entities
This means the account associated with your API key doesn't have read access to that entity. In Concord, check that the user account tied to your API key has the appropriate role — admin or owner-level access is typically required to read organization-wide data like Organization members or User organizations.
## Data discrepancies
Agreement counts in Coupler.io don't match what I see in the Concord UI
The Concord UI may show agreements from multiple organizations if you're a member of several. Your API key is scoped to a specific organization, so it only returns agreements from that org. If you need data from multiple orgs, create separate data flows with API keys for each organization and use an Append transformation to combine them.
## Rate limits
My data flow is slow or times out on large agreement sets
Concord's API enforces rate limits that can slow down syncs when you have a large number of agreements. If you're hitting delays, try scheduling syncs during off-peak hours or splitting large pulls across multiple data flows by entity. Coupler.io's Airbyte-based connector handles pagination automatically, but very large datasets will still take longer.
---
# 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/finance-and-accounting/concord/common-issues.md?ask=&goal=
```
`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.