> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/consumer-service/environments-and-base-url.md).

# Environments & Base URL

## Environment

There is a single **production** environment. There is no sandbox or staging environment.

## Base URLs

Two base URLs are used across this documentation:

| Purpose                         | Base URL                                                               |
| ------------------------------- | ---------------------------------------------------------------------- |
| **All API calls**               | `https://consumer-service-api.fraudcheckonline.co.za/consumer-service` |
| **Authentication** (token only) | `https://consumer-service-api.fraudcheckonline.co.za`                  |

Endpoint paths in each service's documentation are relative to the **API Base URL**. For example, the `/credit-check` endpoint resolves to:

```
https://consumer-service-api.fraudcheckonline.co.za/consumer-service/credit-check
```

## Using BASE\_URL in your code

Store the base URL as a constant so it only appears once in your integration:

{% tabs %}
{% tab title="cURL" %}

```bash
BASE_URL="https://consumer-service-api.fraudcheckonline.co.za/consumer-service"

curl -X POST "$BASE_URL/credit-check" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ ... }'
```

{% endtab %}

{% tab title="Python" %}

```python
BASE_URL = "https://consumer-service-api.fraudcheckonline.co.za/consumer-service"

response = requests.post(
    f"{BASE_URL}/credit-check",
    headers={"Authorization": f"Bearer {access_token}"},
    json={ ... },
)
```

{% endtab %}

{% tab title="JavaScript (Node.js)" %}

```javascript
const BASE_URL = "https://consumer-service-api.fraudcheckonline.co.za/consumer-service";

const response = await fetch(`${BASE_URL}/credit-check`, {
  method: "POST",
  headers: { Authorization: `Bearer ${accessToken}` },
  body: JSON.stringify({ ... }),
});
```

{% endtab %}
{% endtabs %}

## Authentication endpoint

The token endpoint sits at the root URL (no `/consumer-service` path):

```http
POST https://consumer-service-api.fraudcheckonline.co.za/auth/login
```

See [Authentication](/consumer-service/authentication.md) for full 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://docs.fraudcheck.co.za/consumer-service/environments-and-base-url.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.