GP247 API

Name: GP247 API
Brand: GP247 API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontbearer, apiKey2 EndpointsREST

For Agents

Authenticate against a GP247 e-commerce store as a customer or admin and obtain the bearer token used for downstream storefront and admin operations.

Install Jentic One Beta

Connect the GP247 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GP247 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 GP247 API.

Authenticate a storefront customer via POST /front/login and receive a bearer token

Authenticate an administrator via POST /core/login for back-office operations

Combine apiconnection and apikey headers with bearer auth on subsequent requests

GET STARTED

Start building with GP247 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use GP247 API for, with concrete tasks.

★ Storefront Customer Authentication

An agent acting on behalf of a shopper logs in to a GP247 storefront with email and password to receive a bearer token. The token, paired with the store's apiconnection and apikey headers, then gates customer-scoped operations once the rest of the GP247 surface is exposed. The published spec only covers the login step, so non-authentication operations require separate documentation from the store operator.

POST /front/login with the customer's email and password and store the returned bearer token for subsequent requests.

Admin Console Authentication

Back-office tooling and merchant agents authenticate via POST /core/login to obtain an admin bearer token. The admin token is separate from customer tokens and grants access to back-office operations once additional endpoints are wired into the agent. Tokens should be rotated and stored encrypted, especially for multi-tenant deployments where the {domain} differs per store.

POST /core/login with admin credentials and cache the returned token under the {domain} key for that store.

Multi-Tenant Bootstrap for Store Networks

Operators running a network of GP247 stores under different domains use the {domain} placeholder in the base URL to route login calls to the correct tenant. An agent reads the customer's store from a routing table, fills the placeholder, and calls /front/login or /core/login. Cross-store sessions are not supported — each domain issues its own token.

Render the base URL https://{domain}/api with domain=shop.example.com and POST /front/login to authenticate a customer at that tenant.

Agent-Assisted Login via Jentic

An AI assistant integrating a merchant's GP247 store can use Jentic to discover the login operations, load their schemas, and execute against the merchant's domain. Jentic stores the apiconnection and apikey credentials in MAXsystem and injects them at call time, so the agent only handles the user-supplied email and password.

Use the Jentic SDK to search 'log in to a gp247 storefront', load /front/login, and execute with the user's email and password against the configured domain.

Key Endpoints

2 endpoints — gp247 (formerly known as s-cart) is an open-source php e-commerce platform.

METHOD

PATH

DESCRIPTION

POST

/front/login

Customer login — returns a storefront bearer token

POST

/core/login

Admin login — returns a back-office bearer token

POST

/front/login

Customer login — returns a storefront bearer token

POST

/core/login

Admin login — returns a back-office bearer token

Why Jentic?

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

Credential isolation

GP247's three-part credential set — bearer token plus apiconnection and apikey headers — is held in Jentic's MAXsystem vault per merchant domain. The agent never handles the apiconnection or apikey directly; Jentic injects them at execution and persists the bearer token returned by /front/login or /core/login.

Intent-based discovery

Agents search Jentic with intents like 'log in to a gp247 storefront' and Jentic returns /front/login or /core/login with the matching schema, so the agent picks the right endpoint by role rather than reading the API docs.

Time to first call

Direct integration: half a day to wire all three credential headers and handle the multi-tenant {domain} routing. Through Jentic: under 30 minutes once credentials are in the vault.

FAQs

Specific to using GP247 API through Jentic.

What authentication does the GP247 API use?

GP247 uses three security schemes that are combined: an HTTP Bearer token (issued by /front/login or /core/login) plus an apiconnection header and an apikey header. The apiconnection and apikey are issued by the store operator and identify the calling integration. Through Jentic, all three credentials are stored in MAXsystem and injected together at execution time.

What is the difference between /front/login and /core/login?

POST /front/login authenticates storefront customers — typical end-user accounts. POST /core/login authenticates administrators with access to back-office operations. The two endpoints issue different bearer tokens and an admin token cannot be substituted for a customer token, or vice versa.

What are the rate limits for the GP247 API?

The OpenAPI spec does not declare rate limits. Because GP247 is self-hosted, limits depend on the store operator's web server configuration. Treat login as a relatively expensive call and cache the resulting bearer token until it expires rather than re-authenticating per request.

How do I log in to a GP247 store through Jentic?

Search Jentic for 'log in to a gp247 storefront', load POST /front/login, and execute with the customer's email and password. The Jentic SDK injects the apiconnection and apikey headers from the vault and returns the bearer token as part of the response payload.

Why does the base URL contain a {domain} placeholder?

GP247 is multi-tenant — each store runs at its own domain. The base URL https://{domain}/api must have {domain} replaced with the merchant's actual host (for example, shop.example.com) before any call is made. Different domains issue different bearer tokens and apikey pairs.

GP247 API

Connect the GP247 API to your agent

Capabilities

Start building with GP247 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs