What authentication does the Bimbala API use?

The Bimbala API uses HTTP bearer token authentication. You supply the token in the Authorization header as Authorization: Bearer <token>. When called via Jentic, the bearer token is held in your Jentic One instance so the raw value never reaches the agent's context.

Can I create a new resource through the Bimbala API?

Yes. POST /resources accepts a JSON payload describing the new resource and creates it on the platform. GET /resources/{id} can then be used to confirm the new record exists and inspect server-assigned fields.

What are the rate limits for the Bimbala API?

The current spec does not declare explicit numeric rate limits. Treat 429 responses as the signal to back off, and call the Jentic SDK, which retries on 429 with exponential back-off so high-volume jobs do not have to handle this by hand.

How do I list all Bimbala resources through Jentic?

Search Jentic for 'list Bimbala resources', which surfaces GET /resources. Load the schema and execute. The Python flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Can I look up Bimbala users by ID?

Yes. GET /users returns the list of users on the platform, and GET /users/{id} returns a single user record by ID. Both endpoints are read-only in the current spec.

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

Yes. Because you run Jentic One yourself, your own rules decide which Bimbala operations and credentials the agent may use, and by default it can call none of them until you allow specific ones. Since Bimbala puts the resource ID in the URL path (GET /resources/{id}, GET /users/{id}), you can pin the agent to reading a single resource and user records while excluding everything else. Creating a resource via POST /resources is not available to the agent unless you explicitly add that operation, and your stored bearer token is injected at execution time rather than exposed to the agent.