BCE API

Name: BCE API API
Brand: BCE API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbearer53 EndpointsREST

For Agents

Programmatically get auth token, list of companies. Covers 53 operations with bearer authentication.

Use for: I need to auth token, I want to of companies, Search for prod categories, Find all add a new product

Connect the BCE API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BCE API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BCE API API.

get auth token

list of companies

Add a new product

Find a single product

Update a product

GET STARTED

Start building with BCE API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BCE API API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'get auth token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

53 endpoints — updates in this version: <br/> <ul> <li>purchase order list and show api</li> </ul>.

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

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}

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BCE API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get auth token') and Jentic returns the matching BCE API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct BCE API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using BCE API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.