Careemnow Careem POS API
Official vendor OpenAPI document · agent-readyE CommerceOrder Managementoauth224 EndpointsREST
For Agents
Manage Careem Food brands, branches, menu catalogs, operational hours, and live orders for a restaurant POS integration via OAuth 2.0.
Use for: I need to onboard a new restaurant brand to Careem Food, List all branches under our brand and their current visibility on Careem, Push our full menu catalog to Careem with updated prices, Mark item ITEM-22 as out of stock at branch BR-7
Not supported: Does not handle ride-hailing, customer payments, or driver dispatch - use for restaurant brand, branch, catalog, and order management on Careem Food only.
Careem POS API connects restaurant point-of-sale systems to the Careem Food / SuperApp marketplace, automating brand and branch setup, menu catalog publishing, operational hours, and live order flow. It exposes 24 endpoints across brands, branches, catalogs, and orders, and lets a POS integrator update branch visibility on the SuperApp, request preparation-time extensions, tag orders with metadata, and ingest order events end to end. Authentication is OAuth 2.0 client credentials with the `pos` scope, issued by Careem's identity provider.
Install Jentic One Beta
Connect the Careem POS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Careem POS 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.
1
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%2Fcareemnow.com%2Fcareemnow" | sh2
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%2Fcareemnow.com%2Fcareemnow" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Careem POS API.
Create, list, fetch, update, and delete restaurant brands on Careem
Onboard branches and toggle their POS integration and SuperApp visibility status
Publish or reset a full menu catalog and update item availability per branch
Set and fetch branch operational hours including time-bound visibility windows
Stream live orders from Careem, fetch order detail by ID, and progress order state
Request additional preparation time on a specific order to avoid SLA breaches
Tag orders with custom metadata for downstream POS reporting
Use Cases
Patterns agents use Careem POS API for, with concrete tasks.
★ Restaurant POS Integration
Connect a restaurant POS to Careem Food so orders flow into the kitchen system without manual re-entry. The PUT /catalogs endpoint pushes the menu, GET /orders returns live orders, PUT /orders/{order_id} progresses state from accepted through ready, and PUT /orders/{order_id}/delay-request asks for more prep time when needed. This eliminates the manual tablet-style operation Careem flags as the core problem in its API overview.
Poll GET /orders for a branch, accept any new orders by calling PUT /orders/{order_id}, and tag each with the local POS ticket number.
Menu and Catalog Management
Keep menus in sync between an internal product database and the Careem SuperApp. Use PUT /catalogs to publish a full catalog as a single transaction, GET /catalogs/status/{request_id} to confirm processing, and PATCH /catalogs/{catalog_id}/items to flip individual items in or out of stock without resending the whole menu. This avoids the disconnects that lead to canceled orders.
Submit an updated catalog payload via PUT /catalogs, poll the request_id until success, then mark item ITEM-22 unavailable at branch BR-7.
Branch Operations Control
Drive branch state changes from a back-office tool: open or close a branch on the SuperApp, set time-bound closures (e.g., 'closed for 30 minutes'), and update operational hours. POST /branches/{branch_id}/visibility/status and /visibility/status/expiries handle real-time visibility, while PUT /operational-hours covers regular weekly schedules. PATCH /branches/{branch_id}/status toggles the underlying POS integration when a branch goes offline.
Set branch BR-3 to closed for 30 minutes on the SuperApp during an unexpected kitchen issue.
AI Agent Order Operations via Jentic
Wire Careem POS into an operations agent through Jentic so a restaurant manager can ask 'are there any orders waiting more than 5 minutes?' and the agent answers with action. Jentic returns the right operation, holds the OAuth client credentials in its vault, and exposes order, branch, and catalog endpoints as a single tool surface for any framework.
Through Jentic, list orders for branch BR-3, find any in 'accepted' state for over 5 minutes, and request a delay extension on each.
Key Endpoints
24 endpoints — careem pos api connects restaurant point-of-sale systems to the careem food / superapp marketplace, automating brand and branch setup, menu catalog publishing, operational hours, and live order flow.
METHOD
PATH
DESCRIPTION
POST
/token
Generate an OAuth access token
GET
/orders
List orders
GET
/orders/{order_id}
Fetch an order by ID
PUT
/orders/{order_id}
Update order state
PUT
/orders/{order_id}/delay-request
Request more preparation time
PUT
/catalogs
Create or update the full menu catalog
PATCH
/catalogs/{catalog_id}/items
Update item availability
POST
/branches/{branch_id}/visibility/status
Update branch status on the SuperApp
POST
/token
Generate an OAuth access token
GET
/orders
List orders
GET
/orders/{order_id}
Fetch an order by ID
PUT
/orders/{order_id}
Update order state
PUT
/orders/{order_id}/delay-request
Request more preparation time
PUT
/catalogs
Create or update the full menu catalog
PATCH
/catalogs/{catalog_id}/items
Update item availability
POST
/branches/{branch_id}/visibility/status
Update branch status on the SuperApp
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Careem POS API by hand means running the OAuth client-credentials exchange at identity.careem.com, refreshing the access token, and sending it on every call to the apigateway.careemdash.com host yourself. Through Jentic you install once, import the Careem POS API from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Careem puts the order, branch, and catalog ids in the URL path (/orders/{order_id}, /branches/{branch_id}/visibility/status), so a rule can pin your agent to one branch for order reads and updates. You choose the operations it may call, so catalog edits and branch visibility changes are not included unless you add them.
Credential isolation
Your Careem client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the token exchange and injects the resulting access token at execution time. The secrets never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'update a Careem order state' or 'mark a menu item out of stock', and Jentic returns the matching Careem POS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Careem POS API through Jentic.
What authentication does the Careem POS API use?
Careem POS uses OAuth 2.0 client credentials. POST a client_id and client_secret to https://identity.careem.com/token (or the spec's POST /token equivalent) to receive an access token with the `pos` scope, then send it as a bearer token. Through Jentic the client credentials are stored encrypted in the credential vault and the access token is fetched and refreshed automatically.
Can I push a full menu catalog through the Careem POS API?
Yes. PUT /catalogs accepts the full menu as a single payload and returns a request_id. Poll GET /catalogs/status/{request_id} for the upload result, then use PATCH /catalogs/{catalog_id}/items to flip individual items in or out of stock without re-sending the whole catalog.
How do I close a branch temporarily on the Careem SuperApp?
Call POST /branches/{branch_id}/visibility/status to toggle the branch on or off, or POST /branches/{branch_id}/visibility/status/expiries to set a closed window with a specific duration (for example, 30 minutes during a kitchen rush). Both endpoints affect what customers see in the SuperApp immediately.
What are the rate limits for the Careem POS API?
Careem documents rate limiting under the 'Auth rate limiting' tag of its API reference and applies per-client throttling at the gateway. The OpenAPI specification does not publish numeric limits; if you receive 429 responses, slow polling on /orders and back off on bulk catalog updates. Refer to the official Careem POS docs for the current numbers.
How do I receive new orders - webhook or polling?
The OpenAPI surface itself exposes order retrieval through GET /orders and GET /orders/{order_id}, suitable for polling. The Careem documentation also references catalog and order webhook events under the 'Order API webhook events' and 'Catalog API webhook events' tags; configure those out-of-band with Careem to receive push notifications instead of polling.
How do I accept an order through Jentic?
Run `pip install jentic`, then use Jentic's search to find the order-state operation with the query "update careem order state", load the schema, and execute with `{"order_id": "ORD-9001", "state": "accepted"}`. Jentic calls PUT /orders/{order_id} with a fresh OAuth token from the vault and returns Careem's confirmation.
Can I tag orders with my own POS reference?
Yes. PATCH /orders/{order_id}/tags accepts arbitrary metadata you can use to attach a local POS ticket number, kitchen station ID, or operator initials. This is the recommended way to keep Careem orders linked to your own systems for later reporting.
Can I limit what my agent is allowed to do with the Careem POS API?
Yes. Because you run Jentic One yourself, your own rules decide which Careem POS operations and credentials the agent can use, so you can grant it just GET /orders and PUT /orders/{order_id} while withholding PUT /catalogs and the branch visibility endpoints. Careem places the order, branch, and catalog IDs in the URL path (for example /orders/{order_id} and /branches/{branch_id}/visibility/status), so a rule can also pin the agent to a single branch for order reads and state updates. The OAuth client credentials stay with your instance and are never exposed to the agent, so it can only invoke the operations you have allowed.
GET STARTED