> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/developer-docs/hub88-apis/request-structure.md).

# Request structure

## Request URL structure

Hub88 APIs use a straightforward URL naming convention, consisting of two parts, a **base URL** and **endpoint path**.

The API **base URL** is assigned to each Operator or Supplier during onboarding based on their region. The endpoint path is different based on the endpoint that the call is made to or from, and can be seen in the API reference of each endpoint. 

**Request structure example:** 

Structure: `https://{your-assigned-base-url}/{endpoint-path}` 

Example full request URL:  `http://api2.hub88.io/operator/generic/v2/game/url`

Staging environment is available at  `https://api.server1.ih.testenv.io/`

### Base URLs for API requests

* Europe region
  * `api.hub88.io`
* Asia region
  * `api.as1.hub88.io` 
* Latin America region
  * `api.am.hub88.io`


---

# 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.hub88.io/developer-docs/hub88-apis/request-structure.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.