---
title: "Obtaining API Credentials"
space: "TIMs INCOTEX Intergration"
url: "https://docs.navari.co.ke/tims-incotex/obtaining-api-credentials"
updated: "2026-06-09"
---

Before the integration can submit any invoices, your ERPNext instance needs valid credentials to authenticate against your INCOTEX TIMs device, specifically a **Base URL** and an **API Key** (entered later on the [Configuration](https://docs.navari.co.ke/tims-incotex/configuration) page). These credentials are **not** generated inside ERPNext. They are issued by your INCOTEX TIMs supplier, who in Kenya is **Pergamon Group Ltd**.

 

## Why You Need to Request Them 

The INCOTEX device is a KRA-certified Control Unit. Before it can transmit invoices on your behalf, it must be provisioned and registered against your business's KRA PIN, and an API key must be generated for the systems (such as ERPNext) that will communicate with it. That provisioning is handled by the device supplier, not by the end user which is why the Base URL and API Key are obtained by contacting Pergamon Group rather than created from within the app.

## About Pergamon Group 

Pergamon Group Ltd is a Nairobi-based ICT solutions company and an authorized supplier of KRA-approved TIMs and eTIMS hardware and software, including INCOTEX fiscal devices. They handle device supply, KRA compliance setup, and eTIMS integration support, and they are the point of contact for issuing the API credentials this integration requires.

## Contact Details


|              |                                                                             |
| ------------ | --------------------------------------------------------------------------- |
| **Email**    | info@pergamongroup.com                                                      |
| **Phone**    | +254 111 050 950 / +254 112 817 917                                         |
| **WhatsApp** | +254 112 817 917                                                            |
| **Website**  | [https://pergamongroup.com](https://pergamongroup.com/)                     |
| **Office**   | Springette Office Park, Spring Valley, Lower Kabete Road, Block B1, Nairobi |
| **Branches** | Nairobi, Kisii, Eldoret, Mombasa                                            |
| **Hours**    | Monday–Friday, 8:00 a.m. – 5:00 p.m. (EAT)                                  |


 

The fastest route for a credentials request is an email to **info@pergamongroup.com**, copying your account manager if you already have one.

## What to Include in Your Request

To help Pergamon Group provision your device and issue credentials without unnecessary back-and-forth, include the following in your first email:

- **Registered business name** exactly as it appears on your KRA records
- **KRA PIN**
- **INCOTEX device model and serial number**, if you have already purchased a device (if not, mention that you need one supplied)
- **Environment(s) required** `Sandbox` for testing, `Production` for live KRA submissions, or both (requesting both up front is recommended; see below)
- **A technical contact** on your side who will configure ERPNext, so the credentials and endpoint details can be shared directly with them

 

## What You Will Receive 

Once your device is provisioned, Pergamon Group will provide the values you enter on the [Configuration](https://docs.navari.co.ke/tims-incotex/configuration) page:

 


| Credential        | Used For                                                                                                                         |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Base URL**      | The root URL of your INCOTEX device's API                                                                                        |
| **API Key**       | The authentication key for your device                                                                                           |
| **Endpoint URLs** | The specific invoice, credit note, query, and health-check paths (these may be supplied explicitly or derived from the Base URL) |


 

Keep these credentials secure. The API Key authenticates submissions to KRA on your behalf and should be treated like a password and shared only with the people configuring the integration.

 

## Sandbox vs Production

It is good practice to request **Sandbox** credentials first. The Sandbox environment lets you submit test invoices and confirm that the integration is routing calls correctly all this without sending real data to KRA. Once you have verified the full flow (invoice submission, CU number retrieval, QR code generation, and credit notes), switch the **Environment** field to `Production` and enter the live credentials for go-live.

 

## Next Step

After you receive your credentials, continue to the [Configuration](https://docs.navari.co.ke/tims-incotex/configuration) page to enter the Base URL, API Key, and endpoint URLs, then use the **Health Check** button to confirm the device is reachable.