Authentication
Securing your HTTP requests is paramount in ensuring the integrity and confidentiality of data exchanged between clients and servers. Authentication, whether through tokens or API keys, plays a pivotal role in verifying the legitimacy of requests. In this guide, we'll explore the fundamentals of setting up authentication for HTTP requests, focusing on API Key Authentication.
Authentications Method(s)
Regular API Key
Regular API Keys provide comprehensive access similar to a planner account, making them suitable for full system integrations. This is the most common authentication method for integrating RoutiGo with your systems.
Access Level:
Full access to all RoutiGo features and endpoints, equivalent to planner account permissions. Ideal for managing routes, assignments, and accessing all data across your organization.
Implementation:
Add your API key to the request header:
X-API-KEY: your_api_key_hereSupplier API Key
Supplier API Keys grant limited permissions specific to a single supplier, making them ideal for supplier-focused integrations. These keys provide controlled access for external partners or suppliers.
Access Level:
Restricted access limited to supplier-specific operations and data. Perfect for giving suppliers access to manage their own deliveries and assignments without exposing broader system data.
Implementation:
Add your supplier API key to the request header:
X-SUPPLIER-API-KEY: your_supplier_api_key_hereGetting Your API Key
To obtain an API key (Regular or Supplier), please contact our support team. The quickest way is through our live chat, available at the bottom right of our website and dashboard.