> 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/ecommerce/cart/common-issues.md).
# Common Issues
## Connection issues
My API key isn't being accepted
Double-check that you've copied the full API key from Cart.com — it's easy to accidentally include a trailing space or miss a character. Also confirm that the API key belongs to an account with developer or admin-level access. Keys tied to limited-permission accounts may be rejected by the API even if the format looks correct.
Coupler.io says the connection failed but my API key looks correct
Cart.com API keys can be scoped to specific store environments (e.g., staging vs. production). Make sure the key you're using matches the store environment you want to pull data from. If you recently regenerated the key, update it in your Coupler.io data flow source settings.
## Missing data
Some orders aren't showing up in my export
Check the **start date** parameter in your data flow. If you've set a start date that's too recent, older orders will be excluded. Use the date picker to extend the range backward. Also note that Cart.com may have a short delay before very recent orders appear via the API.
Order items or payments are missing for some orders
Order items and order payments are separate entities in Coupler.io. If you're only pulling the Orders entity, you won't automatically get line items or payment details — you need to add Order items and Order payments as separate sources in your data flow, then use the Join transformation to connect them on Order ID.
The Products entity is missing some catalog items
Inactive or archived products may not be returned by the Cart.com API depending on your store's API configuration. Check whether the missing products are set to an inactive or draft status in your Cart.com admin panel.
## Permission errors
I'm getting a 403 Forbidden error
This usually means the API key doesn't have permission to access the requested entity. In Cart.com, confirm that the API user or role associated with the key has read access to the data you're trying to export. You may need to ask your store admin to update the API key's permissions.
## Data discrepancies
Order totals in Coupler.io don't match what I see in Cart.com
Order totals in the Orders entity reflect the values at the time of the API response. If an order was edited, refunded, or had a discount applied after the initial export, re-run your data flow to get the updated values. Scheduled syncs will keep totals current going forward.
Customer cart data looks stale or doesn't match the live cart
The Customers carts entity returns the current cart state at the moment of the API call. It does not store historical snapshots. If you need to track cart changes over time, set up frequent scheduled syncs and append results to a destination table.
## Rate limits
My data flow is timing out or returning partial results
Cart.com's API enforces rate limits that may slow down large data pulls. If you're syncing a large product catalog or many months of orders, try narrowing the start date to reduce the volume of records fetched per run. Coupler.io handles pagination automatically, but very large datasets may require splitting into multiple data flows by date range.
---
# 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/ecommerce/cart/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.