> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-apis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-apis/accessing-os-apis/os-features-api/getting-started.md).

# Getting started

The getting started guide explains how to integrate OS Features API in various open GIS software applications.

This guide explains how to integrate OS Features API in various open GIS (Geospatial Information System) software applications.

{% hint style="info" %}
If you are not familiar with OS Features API, please read the [Overview documentation](/os-apis/accessing-os-apis/os-features-api.md) before proceeding.
{% endhint %}

## What you need?

* One of the GIS software applications listed below
* OS Features API URL and key; see [Getting started with an API project](/os-apis/core-concepts/getting-started-with-an-api-project.md) for more information

## Instructions

You can use any of the applications listed below to integrate with the OS Features API. Click a link to open the instructions on how to integrate with the OS Features API service for each application.

* [ArcGIS Online](/os-apis/accessing-os-apis/os-features-api/getting-started/arcgis-online.md)
* [ArcGIS Pro](/os-apis/accessing-os-apis/os-features-api/getting-started/arcgis-pro.md)
* [ArcMap](/os-apis/accessing-os-apis/os-features-api/getting-started/arcmap.md)
* [Cadcorp SIS](/os-apis/accessing-os-apis/os-features-api/getting-started/cadcorp-sis.md)
* [MapInfo Pro](/os-apis/accessing-os-apis/os-features-api/getting-started/mapinfo-pro.md)
* [QGIS](/os-apis/accessing-os-apis/os-features-api/getting-started/qgis.md)

{% hint style="warning" %}
When using a Premium Plan, it's best not to select lots of features or a large geographic area in your GIS software as this can easily use up API transactions.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-apis/accessing-os-apis/os-features-api/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.