Getting Started

Get up and running with Geo-Engine in just a few minutes.

Prerequisites

Before you start, you'll need:

1. API Key - Contact your Quarticle account manager or visit your dashboard
2. HTTP Client - curl, Postman, or any HTTP library
3. Basic REST Knowledge - Familiarity with HTTP requests and JSON

Step 1: Get Your API Key

1. Contact your Quarticle account manager, or log in to your Geo-Engine Dashboard
2. Navigate to Settings → API Keys
3. Click Generate New Key
4. Copy and store your API key securely

Step 2: Make Your First Request

Let's geocode an address using the Qarta API:

cURL

curl -X GET "https://graph.quarticle.ro/graph/api/v1/places/geocode?q=New%20York" \
  -H "Authorization: YOUR_API_KEY"

JavaScript

const response = await fetch(
  'https://graph.quarticle.ro/graph/api/v1/places/geocode?q=New%20York',
  {
    method: 'GET',
    headers: {
      'Authorization': 'YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);

Python

import requests

headers = {
    'Authorization': 'YOUR_API_KEY'
}

response = requests.get(
    'https://graph.quarticle.ro/graph/api/v1/places/geocode',
    params={'q': 'New York'},
    headers=headers
)

print(response.json())

Expected Response:

{
  "result": {
    "lat": 40.7128,
    "lon": -74.0060,
    "label": "New York, NY, USA",
    "placeId": "abc123",
    "geocodingQuality": "locality"
  }
}

Step 3: Explore the API

• Qarta API Overview - Explore all available capabilities
• Download Postman Collection - Import pre-built requests
• Quickstart Guide - Deep dive into Qarta endpoints

Common Next Steps

• Authenticate Securely - See Authentication Guide
• Handle Errors - Learn about Error Responses
• Check Rate Limits - Review Rate Limiting

Troubleshooting

401 Unauthorized

• Verify your API key is correct
• Check that your API key hasn't expired
• Ensure you're using the Authorization header with your API key directly (no Bearer prefix)

CORS Errors

• CORS errors in the browser are a strong signal that you are calling the API with the API key exposed in client-side code — this is a security risk. The API key must only be used server-side
• Route browser requests through a backend proxy that attaches the key: see the GeoServer Proxy or Full API Proxy guides
• For server-to-server integrations, use direct HTTP requests

Need Help?

• Browse Guides for common use cases
• Contact support