Install Jentic One Beta

Connect the GoBiz Open API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoBiz Open 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgobiz.co.id%2Fgobiz" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgobiz.co.id%2Fgobiz" | 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 GoBiz Open API.

Push or refresh a GoFood outlet menu via the v2 catalog endpoint

Update menu item and variant stock levels so unavailable items disappear from GoFood

Mark a GoFood order as food-prepared so the courier can be dispatched

Create, retrieve, and manage outlet-level food promotions on GoFood

Query a QRIS payment transaction by ID for reconciliation

GET STARTED

Start building with GoBiz Open API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GoBiz Open API for, with concrete tasks.

★ POS-to-GoFood Menu Sync

Indonesian restaurant POS systems use the GoBiz Open API to keep GoFood menus aligned with the in-store catalogue. The /integrations/gofood/outlets/{outlet_id}/v2/catalog endpoint accepts the latest menu, while the v2 menu_item_stocks and variant_stocks endpoints push stock updates so out-of-stock items disappear from the customer app within seconds.

Push the latest menu and stock levels for outlet ID 8821 to GoFood via the v2 catalog and v2 menu_item_stocks endpoints.

Order Preparation Workflow

When a kitchen display system marks an order as ready, the integration calls /integrations/gofood/outlets/{outlet_id}/v1/orders/{order_type}/{order_number}/food-prepared so GoFood dispatches a courier. This closes the loop between the kitchen and the rider network without manual confirmation.

Mark order 99012 of type 'gofood' as food-prepared for outlet 8821 once the kitchen completes preparation.

Promotion and Payment Reconciliation

Multi-outlet operators run targeted promotions and reconcile QRIS payments centrally. The /integrations/promo and /integrations/payment endpoints let an agent create or cancel a promo and look up specific QRIS transactions for finance reconciliation, all without using the GoBiz dashboard.

Create a 20% off lunch promotion for outlet 8821 effective tomorrow and reconcile yesterday's QRIS transactions.

AI Agent Outlet Operations

An AI agent uses Jentic to automate daily outlet operations: it pushes menu changes, marks orders prepared, and answers staff questions about today's QRIS settlements. Jentic isolates the bearer token from the agent context.

Search Jentic for 'sync gofood menu', load the schema, and push today's menu updates for all four of the merchant's outlets.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for gobiz open api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/integrations/gofood/outlets/{outlet_id}/v2/catalog

Push the full GoFood menu for an outlet

POST

/integrations/gofood/outlets/{outlet_id}/v2/menu_item_stocks

Update menu item stock levels

POST

/integrations/gofood/outlets/{outlet_id}/v2/variant_stocks

Update variant-level stock levels

POST

/integrations/gofood/outlets/{outlet_id}/v1/orders/{order_type}/{order_number}/food-prepared

Mark a GoFood order as prepared

POST

/integrations/promo/outlets/{outlet_id}/v1/food-promos

Create a food promotion for an outlet

GET

/integrations/payment/outlets/{outlet_id}/v2/transactions

List QRIS transactions for an outlet

GET

/integrations/payment/outlets/{outlet_id}/v1/transactions/{transaction_id}

Look up a specific QRIS transaction

POST

/integrations/partner/v1/notification-subscriptions

Subscribe to partner notifications

PUT

/integrations/gofood/outlets/{outlet_id}/v2/catalog

Push the full GoFood menu for an outlet

POST

/integrations/gofood/outlets/{outlet_id}/v2/menu_item_stocks

Update menu item stock levels

POST

/integrations/gofood/outlets/{outlet_id}/v2/variant_stocks

Update variant-level stock levels

POST

/integrations/gofood/outlets/{outlet_id}/v1/orders/{order_type}/{order_number}/food-prepared

Mark a GoFood order as prepared

POST

/integrations/promo/outlets/{outlet_id}/v1/food-promos

Create a food promotion for an outlet

GET

/integrations/payment/outlets/{outlet_id}/v2/transactions

List QRIS transactions for an outlet

GET

/integrations/payment/outlets/{outlet_id}/v1/transactions/{transaction_id}

Look up a specific QRIS transaction

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the GoBiz Open API by hand means exchanging partner bearer tokens and mapping its versioned GoFood catalog, stock, order, and payment endpoints yourself. Through Jentic you install once, import the GoBiz Open API from the API Directory, store the token once, and your agent calls it.

Permission scoping

GoBiz puts the outlet id in the URL path (/integrations/gofood/outlets/{outlet_id}/...), so a rule can pin your agent to one outlet: it can sync that outlet's menu, stocks, and orders and nothing else. You choose the operations it may call, so it creates promos or reads payment transactions only when you include those operations.

Credential isolation

Your GoBiz partner 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.

Intent-based discovery

Agents search Jentic by intent such as 'sync a GoFood menu' or 'read outlet transactions', and Jentic returns the matching GoBiz operation with its input schema so the agent calls the right endpoint without reading the HTML reference.

FAQs

Specific to using GoBiz Open API through Jentic.

Why is there no official OpenAPI spec for GoBiz Open API?

GoBiz publishes HTML reference documentation but does not ship an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GoBiz Open API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the GoBiz Open API use?

GoBiz uses HTTP bearer token authentication. Tokens are issued through GoBiz's partner onboarding process. Through Jentic, the bearer token is stored encrypted in the vault and never exposed to the agent context.

Can I update GoFood stock with the GoBiz Open API?

Yes. POST /integrations/gofood/outlets/{outlet_id}/v2/menu_item_stocks updates stock for menu items, and POST /integrations/gofood/outlets/{outlet_id}/v2/variant_stocks updates variant-level stock. Use these to remove sold-out items from the GoFood app in near real time.

What are the rate limits for the GoBiz Open API?

The OpenAPI spec does not declare numeric rate limits. GoBiz documents per-partner limits in its onboarding agreement; in practice, batch stock updates and back off on HTTP 429 responses.

How do I mark a GoFood order as prepared through Jentic?

Run a Jentic search for 'mark gofood order as prepared', load the schema for POST /integrations/gofood/outlets/{outlet_id}/v1/orders/{order_type}/{order_number}/food-prepared, and execute it with the outlet and order identifiers. Install with pip install jentic.

Does the GoBiz Open API support QRIS payment lookups?

Yes. GET /integrations/payment/outlets/{outlet_id}/v1/transactions/{transaction_id} returns a single QRIS transaction, and the v2 transactions endpoint lists transactions for an outlet for reconciliation.

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

Yes. Because you run Jentic One yourself, your own rules decide which GoBiz operations and credentials the agent can use. Since the outlet id sits in the URL path (/integrations/gofood/outlets/{outlet_id}/...), you can pin the agent to a single outlet and let it sync only that outlet's menu, stock, and orders. You also choose which operations it may call, so it creates food promotions or reads QRIS payment transactions only when you grant those endpoints.

GoBiz Open API

Name: GoBiz Open API
Brand: GoBiz Open API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceOrder Managementbearer14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Sync GoFood menus, mark orders as prepared, query QRIS transactions, and manage food promotions for an Indonesian merchant outlet. Built for POS and ordering integrations.

Use for: Sync the menu for a GoFood outlet from our POS system, Update stock for a GoFood menu item that just sold out, Mark a GoFood order as prepared and ready for pickup, Create a food promotion for an outlet for tomorrow

Not supported: Does not handle GoRide logistics, customer-facing app features, or non-GoFood marketplaces - use for GoFood outlet integrations and QRIS lookups only.

Jentic publishes the only available OpenAPI specification for GoBiz Open API, keeping it validated and agent-ready. The GoBiz Open API is Gojek's merchant integration surface for connecting Indonesian point-of-sale and ordering systems to GoFood, QRIS payments, in-app promotions, and outlet management. It exposes catalog and stock sync, order preparation callbacks, food promotion creation, QRIS transaction queries, and partner notification subscriptions. It is used by POS vendors, kitchen display systems, and back-office tools that need bidirectional sync with a GoFood outlet.

Jentic One on Github View OpenAPI Document

Connect the GoBiz Open API to your agent

Capabilities

Start building with GoBiz Open API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

GoBiz Open API