Open Government, Lithuania Authentication: API Access (2026)

Authentication overview

Authentication for the Open Government, Lithuania API platform enables developers, researchers, and other users to programmatically access the various datasets made available by the Lithuanian government. The platform, established in 2017, serves as a central hub for public sector information, facilitating data-driven research and application development. Access to the API requires proper authentication to ensure data integrity, track usage, and manage resource allocation.

The primary method for authenticating with the Open Government, Lithuania API is through the use of API keys. These keys serve as unique identifiers and secret tokens, allowing the platform to verify the identity of the requesting application or user. API keys are generally suitable for client-server architectures where the key can be securely stored on the server side or for public data access where the risk of key exposure is mitigated by rate limiting and strict access policies. For Open Government, Lithuania, obtaining an API key is a prerequisite for any programmatic interaction beyond simple browsing of the public interface.

The platform's approach to authentication is designed to balance accessibility for public data consumers with the necessity of maintaining control and oversight over data consumption. While the data itself is publicly available, authentication helps monitor usage patterns, enforce usage policies, and provide support. Users are expected to manage their API keys responsibly, adhering to security best practices to prevent unauthorized access to their allocated API resources or potential misuse.

Supported authentication methods

The Open Government, Lithuania API platform supports API key authentication as its primary method. This method involves generating a unique string of characters that acts as a secret token. When making requests to the API, this key must be included in the request, typically in a header or as a query parameter. The platform then validates this key against its records to determine if the request is authorized.

API keys are a common and straightforward method for API authentication, particularly for public APIs where the data being accessed is not highly sensitive but requires some level of access control and usage tracking. They offer a good balance between ease of implementation for developers and basic security for the API provider. However, the security of API keys heavily relies on how they are stored and transmitted by the user. Best practices dictate that API keys should be treated as sensitive credentials, similar to passwords, and protected from unauthorized disclosure.

The following table outlines the supported authentication method, its typical use cases, and the associated security level:

It is important to note that while API keys provide a mechanism for access control, they do not inherently offer user-specific authentication or granular permission management beyond what is configured for the key itself. For most interactions with the Open Government, Lithuania platform, an API key is sufficient for retrieving data.

Getting your credentials

To obtain an API key for the Open Government, Lithuania platform, users typically need to complete a registration process on the official website. This process usually involves creating a user account, which then grants access to a developer portal or a dedicated section where API keys can be generated and managed.

The general steps to acquire your API key are:

1. Visit the Open Government, Lithuania Portal: Navigate to the official Open Government, Lithuania homepage.
2. Register for an Account: Look for a 'Register' or 'Sign Up' option. You will likely need to provide an email address, create a password, and agree to the platform's terms of service.
3. Verify Your Account: An email verification step may be required to activate your account. Check your inbox for a confirmation link.
4. Access the Developer Section: Once logged in, navigate to a section typically labeled 'API Access', 'Developer Settings', or similar. The platform's help page is a good starting point to locate specific instructions.
5. Generate API Key: Within the developer section, there should be an option to generate a new API key. The platform may allow you to name your key for easier management, especially if you plan to use multiple keys for different applications.
6. Store Your Key Securely: Once generated, the API key will be displayed. Copy this key immediately and store it in a secure location. Many platforms will only display the key once upon creation, after which it cannot be retrieved again, only regenerated.

Users should review the official Open Government, Lithuania documentation for the most accurate and up-to-date instructions on credential acquisition, as specific steps and interface elements may evolve over time. It is crucial to treat your API key as a confidential secret, as its exposure could lead to unauthorized use of your API quota or access to data.

Authenticated request example

Once you have obtained your API key from the Open Government, Lithuania platform, you can include it in your API requests. The most common method is to pass the API key as a header in your HTTP request. Below is an example using curl, a common command-line tool for making HTTP requests.

Assume your API key is YOUR_API_KEY_HERE and you want to access a hypothetical endpoint for a list of public institutions:

curl -X GET \
  'https://api.opendata.gov.lt/v1/institutions' \
  -H 'Authorization: Bearer YOUR_API_KEY_HERE' \
  -H 'Accept: application/json'

In this example:

• -X GET specifies the HTTP method (GET, used for retrieving data).
• 'https://api.opendata.gov.lt/v1/institutions' is the hypothetical API endpoint you are targeting. You would replace this with the actual endpoint for the dataset you wish to access.
• -H 'Authorization: Bearer YOUR_API_KEY_HERE' is the HTTP header that carries your API key. The Bearer scheme is a common convention for sending tokens, where YOUR_API_KEY_HERE should be replaced with your actual, securely obtained API key.
• -H 'Accept: application/json' indicates that you prefer the response in JSON format.

Some APIs might also accept the API key as a query parameter. If this were the case, the curl request might look like this (consult the specific API documentation for confirmation):

curl -X GET \
  'https://api.opendata.gov.lt/v1/institutions?apiKey=YOUR_API_KEY_HERE' \
  -H 'Accept: application/json'

Always refer to the specific Open Government, Lithuania API documentation for the exact method of including the API key in requests, as implementations can vary. Incorrect placement or formatting of the API key will result in authentication failures (e.g., HTTP 401 Unauthorized errors).

Security best practices

Securing your API keys and authenticated access to the Open Government, Lithuania platform is crucial to protect your applications and ensure the integrity of your data interactions. Adhering to established security best practices can mitigate risks such as unauthorized access, data breaches, and service interruptions.

1. Treat API Keys as Sensitive Credentials: Your API key provides access to the platform's resources. Treat it with the same level of confidentiality as you would a password. Do not hardcode API keys directly into your source code, especially for client-side applications or public repositories.
2. Environment Variables for Storage: For server-side applications, store API keys as environment variables rather than directly in configuration files. This prevents them from being accidentally committed to version control systems like Git. Many programming languages and frameworks provide mechanisms for accessing environment variables securely.
3. Use HTTPS for All API Calls: Always ensure that all your API requests to https://api.opendata.gov.lt use HTTPS. HTTPS encrypts the communication channel between your application and the API server, preventing eavesdropping and tampering of your API key and other data in transit. The Transport Layer Security (TLS) protocol, which HTTPS relies on, is essential for secure web communication.
4. Implement Server-Side Authentication: If you are building a client-side application (e.g., a web or mobile app), avoid directly exposing your API key to the client. Instead, route API requests through your own secure backend server. Your server can then add the API key before forwarding the request to the Open Government, Lithuania API. This ensures the API key never leaves your controlled server environment.
5. Regular Key Rotation: Periodically rotate your API keys. This means generating a new key and updating all your applications to use the new key, then revoking the old one. Regular rotation minimizes the window of opportunity for a compromised key to be exploited. The recommended frequency for rotation can vary, but quarterly or bi-annually is often a good practice.
6. Implement Rate Limiting and Monitoring: Monitor your API usage for unusual patterns or spikes that could indicate a compromised key or malicious activity. Implement your own rate limits on your application's calls to the Open Government, Lithuania API to prevent abuse, even if the platform itself has rate limits.
7. Restrict Key Permissions (if available): If the Open Government, Lithuania platform offers granular permissions for API keys (e.g., read-only access, access to specific datasets), configure your keys with the least privilege necessary for your application's function. This minimizes the impact if a key is compromised.
8. Secure Your Development Environment: Ensure that your development machines and build pipelines are secure. Malicious software or insecure configurations in your development environment could expose API keys.
9. Error Handling: Implement robust error handling in your application to gracefully manage authentication failures. Avoid logging API keys or sensitive information in publicly accessible logs. When an API key is rejected, log only enough information to troubleshoot the issue without exposing credentials.

By diligently applying these security practices, you can significantly enhance the security posture of your applications interacting with the Open Government, Lithuania API.