> 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.md).

# JSON

The JSON destination in Coupler.io generates a stable, publicly accessible URL that serves your data as a JSON file. Every time your data flow runs, the URL updates with fresh data — making it easy to feed any tool, script, or API that consumes JSON.

This is one of the most flexible destinations available. If your target tool isn't natively supported by Coupler.io, there's a good chance it can read from a JSON endpoint.

## Why use JSON as a destination?

* **Universal compatibility** — any tool that can make an HTTP request can consume your data, including custom scripts, webhooks, and low-code platforms
* **Stable URL** — the link never changes between runs, so you set it up once in your target tool, and data refreshes automatically
* **No authentication setup on the destination side** — no database credentials, no OAuth, just a URL with an access token
* **Works with any Coupler.io source** — pull data from HubSpot, Shopify, Google Ads, Asana, or any other supported source and expose it as JSON

## Prerequisites

* Your target tool or script must be able to make GET requests to an HTTPS URL

## Quick start

{% hint style="success" %}
The JSON destination requires almost no configuration on the destination side — most of the work happens in your source setup. Focus on getting your source data right before generating the URL.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Add a source to your data flow.** Log in to Coupler.io and create a new data flow. Select your data source (for example, HubSpot, Shopify, or Google Analytics) and configure it to pull the data you need.
{% endstep %}

{% step %}
**Select JSON as the destination.** In the destination step of your data flow setup, choose **JSON** from the list of available destinations.
{% endstep %}

{% step %}
**Generate the integration URL.** Click **Generate link**. Coupler.io will create a unique URL for your data flow. This URL is stable — it stays the same across every run, while the data it serves updates each time the flow runs.
{% endstep %}

{% step %}
**Run the data flow.** Click **Save and Run** to execute the data flow for the first time. This initial run is required to populate the URL with data. The JSON endpoint will return a 404 error until at least one successful run has completed.
{% endstep %}

{% step %}
**Copy and use your URL.** Once the run completes, copy the generated URL. Paste it into Postman, your custom script, or any other tool that consumes JSON. The data will be available immediately.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
If you ever need to invalidate the current URL (for example, if the access token was exposed), click **Update** to generate a new link. Any integrations using the old URL will need to be updated.
{% endhint %}

## Supported features

| Feature              | Supported |
| -------------------- | --------- |
| Replace mode         | Yes       |
| Append mode          | No        |
| Automatic scheduling | Yes       |
| Type enforcement     | No        |
| Templates            | No        |


---

# 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.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.