# bunq API Objects

No matter what kind of integration you’re building, you’ll be working with a few essential objects that make up the bunq ecosystem. While the general idea behind each one is straightforward, some names or relationships might seem a little unexpected—mainly because the public API is built on top of the same system that powers the bunq app itself.

Here are the main objects you’ll need to get familiar with (by ID):

* [**User**](/basics/bunq-api-objects/user.md)
* [**MonetaryAccount**](/basics/bunq-api-objects/monetary-account.md)
* [**Payment**](/basics/bunq-api-objects/payment.md)
* [**RequestInquiry**](/basics/bunq-api-objects/requestinquiry.md)
* [**Card**](/basics/bunq-api-objects/card.md)
* [**Attachment**](/basics/bunq-api-objects/attachment-and-note-attachment.md)
* [**NoteAttachment**](/basics/bunq-api-objects/attachment-and-note-attachment.md)

Let’s take a closer look at each of them and see how they fit together.

<figure><img src="/files/ERuYzkSqknady9v2v8As" alt=""><figcaption><p>Entity relation graph</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://doc.bunq.com/basics/bunq-api-objects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.