website logo
⌘K
🚀Getting Started
Welcome Developers
Web integration Architecture
Integration Prerequisite
🔐Authentication
📌Sandbox and Live Environment
🛠️Integration Options
POS Integration Guide
Direct API integration Guide
⚙️Plugins
🇲🇾Malaysia
🇸🇬Singapore
🛍️Marketing brand guide
🔍Logo introduction
🖥️Sitewide
👗Product & service pages
👜Checkout and cart page
🌐Website Assets
API REFERENCE
Docs powered by archbee 
6min

Authentication

When making API calls to LatitudePay, you will need to authenticate those requests by using your API Keys. You can view your API keys in the Octifi Merchant Console. you can get the api keys for your merchant account as explained in the integration-prerequisite.

Note: Sandbox mode and production mode will have a different set of keys and endpoints.

Syntax



All api's from your server should carry the following header in the HTTP request!

Authorization: Api-Key <private_api_key> or <public_api_key>

Public Api key or Private api key, which one should i use?

Rule of Thumb:

Backend Api's (called from the server) always use Private Keys, Frontend api's (called from browser) always use Public key.

Example:

checkout api is a frontend api

Hence it should carry public_api_key in the header

charge api is a backend server side api

Hence it should carry private_api_key in the header







Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Web Integration guide
Docs powered by archbee 
TABLE OF CONTENTS
Syntax
Public Api key or Private api key, which one should i use?
Rule of Thumb:
Example:
checkout api is a frontend api
charge api is a backend server side api