# Reveal an API Component

Revealing an API component is basically the same as [revealing a process](/boomi-console/command-collection/reveal-a-process.md). However, an API might have many, many service processes, which are: [*independent* children](/boomi-console/commands/arguments/common-arguments.md#component-trees)!

There are basically two options to reveal an API.

<div align="left"><figure><img src="/files/WlKw3QH1Fcg43Q3thKKB" alt="" width="369"><figcaption><p>A REST service with its service processes</p></figcaption></figure></div>

### Reveal an API component without its service processes

This command retrieves the API component with its *dependent* child components, only. Dependent child components are *profiles*, *certificates* etc.

```batch
.\bc comp get /c {apiComponentId} /outdir {dir} /t compList.csv /children dependent
```

### Reveal an API component including all its service processes

{% hint style="info" %}
**NOTE**\
Depending on the number of service processes this may take a couple of seconds to retrieve all children.
{% endhint %}

This command retrieves the API component with all child components.

```batch
.\bc comp get /c {apiComponentId} /outdir {dir} /t compList.csv /children all
```


---

# 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://boomi.markusschmidt.pro/boomi-console/command-collection/reveal-a-process-1.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.