canonical: https://jentic.com/apis/swaggerhub.develop-beyable/beyable-activation-machine-to-machine-api

# Develop Beyable BEYABLE Activation machine to machine API

BEYABLE Activation related commands. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically save objective. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Save Objective
- Manage developer tools data programmatically
- Integrate BEYABLE Activation machine to machine API into automated workflows
- Query and filter BEYABLE Activation machine to machine API records by parameters
- Monitor BEYABLE Activation machine to machine API operational status and events

## Use cases

### Developer Tools Operations

Use the BEYABLE Activation machine to machine API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including save objective.

Example prompt: Call POST `/m2m-api/v3/saveobjective` to save objective

### Data Retrieval and Monitoring

Query BEYABLE Activation machine to machine API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary BEYABLE Activation machine to machine API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call BEYABLE Activation machine to machine API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'save objective', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/m2m-api/v3/saveobjective` | Save Objective |

## Key resources

- **m2m-api** — Operations related to m2m-api

## Why Jentic

- **Setup:** Wiring the BEYABLE Activation machine to machine API by hand means setting up its Authorization-header API key, pointing at the activation.beyable.com host, and handling retries yourself. Through Jentic you install once, import the BEYABLE Activation machine to machine API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API exposes a single save-objective operation over a flat path, so scoping is about operations: the agent is limited to the saveobjective call you include and nothing else. You choose whether to grant it at all.
- **Credential handling:** Your BEYABLE API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'save an activation objective', and Jentic returns the matching BEYABLE Activation machine to machine API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the BEYABLE Activation machine to machine API use?

The BEYABLE Activation machine to machine API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I save objective with the BEYABLE Activation machine to machine API?

Yes. Use the POST `/m2m-api/v3/saveobjective` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BEYABLE Activation machine to machine API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I save objective through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'save objective'. Jentic returns the matching BEYABLE Activation machine to machine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BEYABLE Activation machine to machine API have?

The BEYABLE Activation machine to machine API exposes 1 endpoints covering m2m-api operations.

### Can I limit what my agent is allowed to do with the BEYABLE Activation machine to machine API?

Yes. Because you run Jentic One yourself, you decide which BEYABLE operations your agent may call, and this API exposes only a single one: POST `/m2m-api/v3/saveobjective.` If you do not import that operation, the agent cannot reach the API at all; if you do, the save-objective call is the only action it can take. Your BEYABLE API key stays with your own Jentic One instance and is injected at execution time, so the agent never sees the raw credential.