Komerce · Authentication Profile

Komerce Authentication

Authentication

Komerce secures its APIs with apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyShippingLogisticsE-CommercePaymentsQRISIndonesiaCouriersTrackingFulfillment
Methods: apiKey Schemes: 3 OAuth flows: API key in: header

Security Schemes

ApiKeyAuth apiKey
· in: header (x-api-key)
ApiKeyAuth apiKey
· in: header (X-API-Key)
ApiKeyAuth apiKey
· in: header (key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: openapi/komerce-payment-openapi.yml, openapi/komerce-qrisly-openapi.yml, openapi/komerce-shipping-cost-openapi.yml,
  openapi/komerce-shipping-delivery-openapi.yml
docs:
- https://rajaongkir.com/docs/shipping-cost/getting_started/apikey
- https://rajaongkir.com/docs/delivery-order-api/getting_started/api-key
- https://rajaongkir.com/docs/payment-api/getting-started/authentication
- https://rajaongkir.com/docs/qrisly/getting-started/authentication
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
  note: >-
    Every Komerce surface uses a header API key and nothing else — no OAuth 2.0, OIDC, basic,
    bearer or mTLS. Crucially the keys are per-product and NOT interchangeable: the docs warn
    explicitly against using a key issued for one service against another. Keys are issued and
    rotated from the Collaborator dashboard under Developer -> Settings -> Api Key. Sandbox and
    production require separate keys, and a sandbox key will not work in production without
    administrator approval. HTTPS is required.
  issuance: https://collaborator.komerce.id/registration
  dashboard: https://collaborator.komerce.id
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: x-api-key
  description: Payment API key from the Collaborator dashboard — the same key used for Komerce
    Shipping (RajaOngkir). Sandbox keys use the sandbox prefix, production keys the live prefix.
  sources:
  - openapi/komerce-payment-openapi.yml
  - openapi/komerce-shipping-delivery-openapi.yml
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: X-API-Key
  description: QRISLY API key generated from the RajaOngkir Collaborator dashboard (Developer
    -> API Settings -> Generate New API Key).
  sources:
  - openapi/komerce-qrisly-openapi.yml
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: key
  description: Shipping Cost API key from the Collaborator dashboard (Developer -> Settings
    -> Api Key).
  sources:
  - openapi/komerce-shipping-cost-openapi.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/komerce-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.