> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/exports/client.md).

# Client Exports

## OpenMarketplace

```lua
exports['daddy-marketplace']:OpenMarketplace(locationId)
```

Opens the marketplace UI for one location. `locationId` is a key from `Config.Locations`. Unknown ids are ignored — nothing happens and no error is thrown.

```lua
exports['daddy-marketplace']:OpenMarketplace('main_market')
```

Use it to open the market from a phone app, a job menu, or your own interaction resource.

{% hint style="info" %}
The server re-checks the player's distance to that location (`Config.Security.distanceCheck`) and the location's `enabledJobs` / `disabledJobs` before allowing any action, so this export cannot be used to trade from across the map.
{% endhint %}

## CloseMarketplace

```lua
exports['daddy-marketplace']:CloseMarketplace()
```

Closes the UI and releases the NUI focus. Safe to call when it is already closed.

Useful when another resource needs the screen — for example, closing the market before opening your own full-screen menu.

## IsMarketplaceOpen

```lua
exports['daddy-marketplace']:IsMarketplaceOpen()
```

Returns `true` while the UI is open, `false` otherwise.

Use it to suppress your own HUD, menus or keybinds while the player is trading:

```lua
if exports['daddy-marketplace']:IsMarketplaceOpen() then return end
```

## Example: a phone app entry

```lua
RegisterNUICallback('openMarketFromPhone', function(_, cb)
    exports['daddy-marketplace']:OpenMarketplace('main_market')
    cb({})
end)
```

The player still has to be standing at `main_market` for the server to accept any action — this only saves them the click on the NPC.

## Next steps

* [Server Exports](/daddy-studios-docs/scripts/daddy-marketplace/exports/server.md)
* [Config Hooks](/daddy-studios-docs/scripts/daddy-marketplace/hooks.md)


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/exports/client.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.