> For the complete documentation index, see [llms.txt](https://fair-indonesia.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fair-indonesia.gitbook.io/docs/developers/api-reference.md).

# API Reference

The Fair API is organized into product families. Every endpoint is REST, returns JSON, and is called the same way — only the path changes.

**Base URL**

```
https://api.fair-indonesia.com/api/fairservice        (production)
https://stg.api.fair-indonesia.com/api/fairservice    (staging — use for free trials)
```

**Authentication**

Every request needs your API token in the `Authorization` header. Pass the token value directly — there is **no `Bearer` prefix**.

```
Authorization: <your_token>
```

See [Authentication](/docs/developers/authentication.md) for full details and [Core Concepts](/docs/developers/concepts.md) for environments, pagination, errors, and how asynchronous jobs work.

Each family page renders directly from the [Fair OpenAPI spec](https://github.com/lightwaslost/fair-docs/blob/main/developers/api-reference/fair-openapi.yaml), so every endpoint has full request and response schemas with examples, generated directly from the spec.

***

## Product families

| Family                                                                                   | What it does                                                                                                  |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [Creator Search & Analytics](/docs/developers/api-reference/creator-search-analytics.md) | Discover creators across 400M+ profiles, analyze audiences, look up contacts, and resolve emails to profiles. |
| [Purchase Intent](/docs/developers/api-reference/purchase-intent.md)                     | Score whether a creator's audience shows real buying intent.                                                  |
| [Comments Relevance](/docs/developers/api-reference/comments-relevance.md)               | Identify which comments on a post are relevant to a product or topic.                                         |
| [Social Background Check](/docs/developers/api-reference/social-background-check.md)     | Risk-score profiles, content, and media for brand safety, with flagging criteria and continuous monitoring.   |
| [Content & Comments](/docs/developers/api-reference/content-and-comments.md)             | Fetch public content and comments for a profile or single item, including LinkedIn.                           |
| [Social Listening](/docs/developers/api-reference/social-listening.md)                   | Track the conversation around a brand, topic, or hashtag.                                                     |

> **Async products** (search export, profile analytics, email lookup, audience overlap, purchase intent, comments relevance, screening, social listening) follow a submit-then-fetch pattern: a `POST` returns an `id`, and you poll `GET .../{id}` until the result is ready. See [Core Concepts](/docs/developers/concepts.md#synchronous-vs-asynchronous-endpoints).

## Related

* [Quickstart](/docs/developers/quickstart.md) — your first call in five minutes
* [Core Concepts](/docs/developers/concepts.md) — environments, async jobs, pagination, errors
* [Authentication](/docs/developers/authentication.md) — how to get and use your API token
* [Dictionaries](/docs/developers/dictionaries.md) — shared lookups for search filters


---

# 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://fair-indonesia.gitbook.io/docs/developers/api-reference.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.