What authentication does the Feature Watch API use?

The API supports a bearer token obtained via POST /login and an X-API-Key header. Through Jentic the credential is stored in the vault and injected at call time so the raw token never enters agent context.

Can I create features programmatically with the Feature Watch API?

Yes. POST /features accepts a title, description, and board association, and POST /add_feature provides an alternative add operation for legacy clients.

What are the rate limits for the Feature Watch API?

Feature Watch does not publish numeric rate limits in the spec. Apply exponential backoff on 429 responses and cache list results between polls to reduce request volume.

How do I list features on a board through Jentic?

Run pip install jentic, search 'list feature watch board features', load GET /board/{id}/features, and execute it with the target board ID to receive the feature list.

Does the Feature Watch API support webhooks?

Yes. The Webhooks tag exposes endpoints for registering callback URLs that receive feature activity events, removing the need to poll for changes.

Can I limit what my agent is allowed to do with the Feature Watch API?

Yes. Because you run Jentic One yourself, your own rules decide which Feature Watch operations and credentials the agent may use. Since Feature Watch puts the board and feature id in the URL path, such as /board/{id}/features and /feature/{id}, you can pin the agent to a single board and keep board, feature, and comment reads read-only. Write operations like POST /features are available only when you explicitly add them, so the agent files new features only if you allow it.