canonical: https://jentic.com/apis/swaggerhub.advancedcomputersoft/bce-api # Advancedcomputersoft BCE API Updates in this version:
. The API exposes 53 endpoints secured with bearer authentication. ## For AI agents Programmatically get auth token, list of companies. Covers 53 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for e-commerce only. ## Capabilities - get auth token - list of companies - Add a new product - Find a single product - Update a product ## Use cases ### E-Commerce Operations Use the BCE API to perform e commerce operations programmatically. The API provides 53 endpoints covering core functionality including get auth token, list of companies, list prod categories. Example prompt: Call POST /auth/user to get auth token ### Automated authentication Management Automate authentication operations by combining multiple BCE API endpoints. Agents can list of companies and then list prod categories in a single workflow. Example prompt: Call GET /companies to list of companies, then verify the result ### AI Agent Integration via Jentic AI agents discover and call BCE 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 bearer tokens manually. Example prompt: Search Jentic for 'get auth token', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /auth/user | get auth token | | GET | /companies | list of companies | | GET | /products/categories | list prod categories | | POST | /products | Add a new product | | GET | /products | list catalogue items | | GET | /products/{product_code} | Find a single product | | PUT | /products/{product_code} | Update a product | | POST | /customers | Add customer | ## Key resources - **authentication** — Operations related to authentication - **product** — Operations related to product - **customer** — Operations related to customer - **company** — Operations related to company - **order** — Operations related to order ## Why Jentic - **Setup:** Wiring the BCE API by hand means calling /auth/user for a bearer token, attaching it to every request, and managing product, category, and customer calls across its SwaggerHub host variants yourself. Through Jentic you install once, import the BCE API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** The BCE API puts the product code in the URL path (/products/{product_code}), so a rule can pin your agent to one product for reads and updates. You choose the operations it may call, so writes like creating a product or a customer are not included unless you add them. - **Credential handling:** Your BCE bearer token 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 'get an auth token' or 'list products', and Jentic returns the matching BCE operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify** — Alternative e commerce API - **Stripe** — Alternative e commerce API ## FAQ ### What authentication does the BCE API use? The BCE API uses a Bearer token 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 get auth token with the BCE API? Yes. Use the POST /auth/user endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the BCE 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 get auth token through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get auth token'. Jentic returns the matching BCE API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the BCE API have? The BCE API exposes 53 endpoints covering authentication, product, customer operations. ### Can I limit what my agent is allowed to do with the BCE API? Yes. Because you run Jentic One yourself, your own rules decide which BCE API operations and credentials the agent may use. Since the product code sits in the URL path (/products/{product_code}), you can pin the agent to reading and updating a single product, and you choose exactly which operations it can call. Write operations such as POST /products to create a product or POST /customers to add a customer stay off-limits unless you explicitly grant them.