Can I create API tokens for automated backup jobs?

Yes. POST /access/users/{userid}/token/{token-name} creates a token scoped to that user's permissions. Tokens can be used directly in API calls without session management. You can list all tokens via GET /access/users/{userid}/token and revoke individual tokens via DELETE.

What are the rate limits for the Proxmox Backup Server API?

PBS does not impose explicit per-endpoint rate limits as it is a self-hosted solution. Performance depends on your server resources. However, authentication ticket creation (POST /access/ticket) applies a per-IP throttle to prevent brute-force attacks.

How do I manage user permissions through Jentic?

Search Jentic for 'set Proxmox backup permissions', load the schema for PUT /access/acl, and execute with the path, user, and role. Jentic handles the cookie authentication and CSRF token injection automatically, returning the updated ACL configuration.

Does the PBS API support OpenID Connect authentication?

Yes. The API provides POST /access/openid/auth-url to generate an OpenID authentication URL and POST /access/openid/login to complete the login flow. This enables SSO integration with identity providers like Azure AD, Keycloak, and Google Workspace.

Can I limit what my agent is allowed to do with the Proxmox Backup Server API?

Yes. You run Jentic One yourself, and your own rules decide which Proxmox Backup Server operations and credentials your agent may use. Because this API puts the datastore in the URL path (/admin/datastore/{store}/...) and the user in /access/users/{userid}/..., you can pin the agent to a single datastore or user so it only reads that store's active operations. State-changing calls such as creating users via POST /access/users or updating the access control list via PUT /access/acl stay off limits unless you explicitly grant them.