> 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/destinations/categories/api/json/faq.md).

# FAQ

<details>

<summary>What is the JSON destination used for?</summary>

The JSON destination generates a stable HTTPS URL that serves your Coupler.io data as a JSON file. You can use this URL to feed data into tools that aren't natively supported by Coupler.io — such as Power BI (via Web connector), custom scripts, automation platforms like Make or Zapier, or any API-based workflow.

</details>

<details>

<summary>Does the URL change every time the data flow runs?</summary>

No. The URL stays the same across every run. Only the data it serves is updated. This means you can configure your downstream tool once and it will always fetch the latest data. If you click **Update** in the destination settings, a new URL is generated and the old one is invalidated.

</details>

<details>

<summary>Why do I get a 404 error when I open the JSON URL?</summary>

The URL returns a 404 until the data flow has completed at least one successful run. Go to your data flow, click **Save and Run**, and wait for the run to finish. After that, the URL will return data.

{% hint style="info" %}
If you're using the JSON destination with Power BI and seeing a 404, this is almost always the cause. See the Power BI destination article for more details.
{% endhint %}

</details>

<details>

<summary>Can I use the JSON destination with Power BI?</summary>

Yes. Paste the integration URL into Power BI's **Get Data → Web** connector. Make sure the data flow has run at least once before doing this, otherwise Power BI will receive a 404 error. Once connected, you can refresh the Power BI dataset to pull in the latest data from Coupler.io.

</details>

<details>

<summary>Is there an Append mode for the JSON destination?</summary>

No. The JSON destination only supports Replace mode — each run overwrites the data at the URL with the latest export. If you need to accumulate historical data over time, consider using a database destination like BigQuery or PostgreSQL instead.

</details>

<details>

<summary>How do I handle nested JSON fields from sources like Shopify or Asana?</summary>

Some sources return fields as nested objects or arrays (for example, Shopify metafields or Asana custom fields). Coupler.io passes these through without automatically flattening them. You can use Coupler.io's transformation features to reshape data before it reaches the destination, or handle the parsing in your consuming tool or script.

</details>

<details>

<summary>Can any Coupler.io source send data to the JSON destination?</summary>

Yes. The JSON destination works with any source available in Coupler.io, including HubSpot, Google Ads, Facebook Ads, Pipedrive, Google Sheets, and more. You can also combine multiple sources in a single data flow using Join, Append, or Aggregate transformations.

</details>

<details>

<summary>Is the JSON URL secure?</summary>

The URL includes an access token that controls who can read the data. Anyone with the full URL can access the exported data, so treat it like a password. Avoid posting it in public places. If the token is compromised, click **Update** in the destination settings to generate a new URL.

</details>

<details>

<summary>How do I test that my JSON URL is working correctly?</summary>

Paste the URL into an HTTP client like Postman, or simply open it in a browser. If the data flow has run successfully, you'll see a JSON array of your data. If you see a 404, the flow hasn't run yet, or the URL has been regenerated.

</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/destinations/categories/api/json/faq.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.