> For the complete documentation index, see [llms.txt](https://api-docs.fcfpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.fcfpay.com/quick-start.md).

# Quick Start

## Authentication

In order to call most of the API endpoints, one needs to obtain an **API\_KEY**. This token is currently obtainable by authenticating yourself to the system.\
The section below describes how to do that.

Once you have obtained your **API\_KEY**, you must include it in all requests that require authentication. You do so by adding a `Authorization` header to the request with the value `Bearer <API_KEY>` as seen in the example on the right.

{% hint style="info" %}
Some API requests are not actually just API endpoints, but the webhook requests, which will be sent to the URL provided by you. So there is not stuff about authentication.
{% endhint %}

## Get an API token

> Note: Please keep in mind, that anytime you must use the API key as a Bearer token.

> For each API request you need to have a token. For getting a token, you need to login to your merchant's dashboard. In case when you don't have an account, you can register here <https://merchant.fcfpay.com/register>.

After logging in to the account, you can retrieve a token by creating a new project in <https://merchant.fcfpay.com/admin/projects/create>.

![Screen taken from development environment, so there is a dummy data just for example.](/files/LAnf3FbziHf5406B4DvC)

Note: keep the token (API key) in a safe place.


---

# 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://api-docs.fcfpay.com/quick-start.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.