# Objects

Across our API endpoints, several key objects are available to interact with, each serving a specific function within the mio.ID ecosystem. Below is a summary of the core objects and links to their detailed descriptions, including fields and use cases:

* [Member](/api-reference/data-dictionary/objects/entity-or-member.md)\
  Represents a registered individual or business in the mio.ID platform.\
  **Use Case:** Interact with individuals or businesses, verify identity, or initiate activities.\
  **Endpoints:** Accessible through Community-related APIs.
* [Activity](/api-reference/data-dictionary/objects/activity.md)\
  Represents requests, sharings, or exchanges initiated by members or businesses.\
  **Use Case:** Create, track, or respond to data-sharing requests between entities.\
  **Endpoints:** Includes APIs to list activities, retrieve details, and create requests.
* [Requirement](/api-reference/data-dictionary/objects/requirement.md)\
  Defines conditions or prerequisites associated with an activity.\
  **Use Case:** Set or retrieve specific requirements necessary to complete an interaction.\
  **Endpoints:** Useful for customizing workflows based on compliance or business logic.
* [Webhook](/api-reference/data-dictionary/objects/webhook.md)\
  Represents a configured endpoint for receiving real-time event notifications.

  **Use Case:** Automate workflows by subscribing to events like activity updates or member changes.\
  **Endpoints:** Manage webhooks to receive notifications for specified events.

For detailed field information, request structure, and usage examples, refer to the respective object documentation in the [API](/api-reference/api-endpoints.md) Developer Guide.


---

# 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://docs-business.mio.id/api-reference/data-dictionary/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.