> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/developers.md).

# Developers

This section is for developers who connect a POS, online store, ERP or app to SensePass.

## What is here

| Section             | Use it to                                                                                                                               |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Transaction API** | Create and manage payments: authentication, payment methods, payment flows, notifications, SDK and iFrames, models, testing and Postman |
| **Partner API**     | Create and manage merchants, locations and other partner objects by API                                                                 |

## Before you start

* Read **How SensePass is organized** in Get started, so you know how partners, merchants, locations, registers and devices fit together.
* Build and test in **Sandbox** first. See **Sandbox and Production** in Get started for the environment URLs.
* Use test credentials and official test cards only in Sandbox.


---

# 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.sensepass.com/sensepay/developers.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.
