# Run via API

After publishing your workflow, you can call it through our API endpoints using your required input parameters to receive a response. For a broad overview of our API capabilities, check out our [API Reference](broken://spaces/rT8WZaGa5JcV0M5osTWg) for detailed technical specifications.

## Authentication

All endpoints require authentication using a Bearer token. To authenticate, include an Authorization header in your request with the value Bearer YOUR\_API\_KEY. You can find your API key in your [Workspace Settings](/your-workspace/workspaces.md#workspace-settings):

<figure><img src="/files/4p6NGwIVA70dpRoncEh1" alt=""><figcaption></figcaption></figure>

## Finding Your Workflow ID

In addition to your API Token, you will also need your Workflow ID to ensure your API calls are reaching the correct endpoint. The Workflow ID is the number found in the app's URL. For instance, in the URL:

```
https://app.airops.com/{your_workspace}/apps/123
```

The Workflow ID is:

```
123
```

Additionally, you can can reference the "Rest API" tab for the Workflow shown further below.

## Endpoints

To find the additional parameters and endpoints available for your Workflow, you can navigate to the "REST API" tab underneath the "Integrate" section of your Workflow:

Ready to make your first request? Check out [API Reference docs](https://developers.airops.com) for further details!

{% @arcade/embed url="<https://app.arcade.software/share/XLLOnL04P09gRC3dAwLv>" flowId="XLLOnL04P09gRC3dAwLv" %}


---

# 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.airops.com/actions/run-once/api.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.