ApivomApivom
Get Demo

Moka POS API Connector

MokaPos's open-platform API for point of sale — businesses, outlets, customers, loyalty programmes, advanced ordering and sales reports — connected to Apivom Iris with the OAuth access token your business obtains from Moka, with every call logged in your tenant.

What you can do

  • Read businesses, outlets, checkout settings and customers for the connected Moka account
  • Loyalty programmes and point activities; advanced-ordering routes incl. auto-accept and order cancellation
  • 68 catalogued routes, 52 read-only — the POS product API, not a raw card-payment gateway
  • Selectable as a provider on Iris payment records; any route tryable from the integrations hub
  • Token endpoint deliberately not proxied: the tenant obtains the OAuth token, Apivom never sees the client secret

Use cases

  • See outlet sales next to the customer account — Pull sales reports and outlet data for a retail or restaurant customer and keep them on the Iris company record for account reviews.
  • Loyalty balance at hand for support — Look up a customer's loyalty programme and point activities from Iris when they call, without opening the POS back office.
  • Order operations from one screen — Check incoming advanced orders, toggle auto-accept for an outlet or cancel an application order from the integrations hub with a confirmation step.

Moka POS is a Turkish point-of-sale platform, and its open-platform API lets a business work with the data behind its tills: the businesses and outlets of an account, checkout settings, customer records, loyalty programmes and point activities, advanced ordering (incoming orders, auto-accept, sales-type generation, cancellation) and sales reporting. It is the POS product API — distinct from Moka's card-acquiring gateway — and contains no raw-card endpoints. Apivom Atlas catalogues 68 of its routes, 52 of them read-only. In Apivom Iris, Moka is a selectable payment provider: the business obtains an OAuth2 access token from Moka with its own client credentials (Apivom intentionally does not proxy the token endpoint, so the client secret never passes through the platform), stores that token in the tenant, and Iris sends it as a Bearer header on each call. Any catalogued route can be run from the integrations hub — reads directly, writes behind a confirmation — with request and response logged in your tenant. Webhook signature verification for Moka is not enabled yet, so inbound notifications are rejected until it is.

Authentication

OAuth2 access token (client-credentials) that your business obtains from Moka's /oauth/token — the token exchange itself is not proxied. Iris sends it as a Bearer header per request; Apivom Atlas stores nothing. Inbound webhook signature verification is not yet enabled and fails closed.

Frequently asked questions

Is this the Moka card-payment gateway?

No. This connector is the MokaPos open-platform API for POS data — businesses, outlets, customers, loyalty, orders and reports. It has no card-payment or PAN endpoints, so it does not change your PCI scope.

Why do I have to obtain the OAuth token myself?

Moka's token endpoint takes your client id and secret. Apivom deliberately leaves that exchange to you so the client secret never crosses the platform; you store only the resulting access token, which Iris sends as a Bearer header and refreshes when you update it.

Are Moka webhooks processed?

Not yet. The per-tenant receiver exists, but Moka's webhook signature verification is not enabled, so inbound notifications are rejected (fail closed) until it is. Payment status is read through the API instead.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.