---
title: Authentication
slug: authentication
icon: 🔐
docTags: 
createdAt: 2021-01-13T06:15:32.000Z
---

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.](https://merchant.octifi.com) you can get the api keys for your merchant account as explained in the [integration-prerequisite](https://docs.sg.latitudepay.com/integration-prerequisite).

:::BlockQuote
**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!`

:::BlockQuote
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:&#x20;

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

### Example:

:::hint{type="success"}
## checkout api is a frontend api

Hence it should carry public\_api\_key in the header
:::

:::hint{type="success"}
## charge api is a backend server side api

Hence it should carry private\_api\_key in the header
:::