# Beam API overview

MK.IO Beam has cloud APIs for fleet and infrastructure management, and a device-local API for channels. Choose the connection that matches the resources you need to manage.

## Cloud APIs

The Fleets and Infrastructure APIs use `https://app.mk.io/` with bearer authentication. Requests are scoped to a project:

<table>
  <thead>
    <tr>
      <th>API</th>
      <th>Path prefix</th>
      <th>Guide</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Fleets</td>
      <td><code>/api/v1/projects/{project_name}/fleet/</code></td>
      <td><a href="/beam/api-guides/how-to/fleets">Fleet workflows</a></td>
    </tr>
    <tr>
      <td>Infrastructure</td>
      <td><code>/api/v1/projects/{project_name}/infra/</code></td>
      <td><a href="/beam/api-guides/how-to/infrastructure/networks-and-sites">Networks and sites</a></td>
    </tr>
  </tbody>
</table>

Use the Infrastructure API to define sites and networks for a deployment. Use the Fleets API to register devices, manage software, and back up or restore device configurations.

Start with [Authentication and connections](/beam/api-guides/getting-started/authentication), then [Your first API call](/beam/api-guides/getting-started/first-api-call).

## Device-local Channels API

The Channels API configures channels on the Beam device. Follow [Connect to a Beam device](/beam/api-guides/how-to/channels/connect-to-a-device) for its connection requirements and [How channels work](/beam/api-guides/how-to/channels/how-channels-work) for its resource model.

## API references

- [Channels API reference](/api-reference/channels-api)
- [Fleets API reference](/api-reference/fleets-api)
- [Infrastructure API reference](/api-reference/infrastructure-api)

For organization, project, and token administration, see the [Management API guides](/mkio/api-guides/how-to/management).