> For the complete documentation index, see [llms.txt](https://toss-ads.gitbook.io/toss-ads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://toss-ads.gitbook.io/toss-ads/release-note/undefined.md).

# 릴리스 노트

<details>

<summary><strong>토스애즈 개발자센터를 오픈했어요</strong> (2026-10-06 등록)</summary>

토스애즈 API 연동에 필요한 가이드를 한곳에 모았어요. [시작하기](/toss-ads/getting-started/api.md) 가이드를 따라 5분 만에 API를 호출해 볼 수 있어요.

제공하는 API는 아래와 같아요.

* [**인증 API**](/toss-ads/references/authentication.md)**:** API 호출에 필요한 Access Token을 발급받아요.
* [**토큰 정보 API**](/toss-ads/references/token-info.md)**:** 발급받은 Access Token에 연결된 Client ID, 권한 범위(scope), 광고계정을 확인해요.
* [**Reporting API**](/toss-ads/references/reporting.md)**:** 광고 성과 데이터를 날짜별, 캠페인별 등 원하는 기준으로 조회해요.&#x20;
* [**Reporting API (Data Spec)**](/toss-ads/references/reporting-data-spec.md)**:** 리포트 조회에 쓸 수 있는 지표와 기준 목록을 확인해요.

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://toss-ads.gitbook.io/toss-ads/release-note/undefined.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.