> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-post-web-app/faq/technical.md).

# Technical

#### Will it work with my technology stack?

It should. To see our list of current integrations click[ here](https://zappost.com/how-it-works#integration), and if you can’t find what you’re looking for then let us know and we might be able to help.

#### Technical Documentation

* Everything from our **ISO27001 certification**, Data Processing Agreements, **GDPR**, data security & compliance policies are all hosted by [Vanta](https://app.vanta.com/retain.me/trust/xxgyxcz915zcv6d6s81brz). You can [request access](https://app.vanta.com/retain.me/trust/xxgyxcz915zcv6d6s81brz) any time.
* Use [API documentation](https://userguide.zappost.com/zap-api/zap-post-api-documentation) and [swagger](https://api.zappost.com/index.html)
* View Zap [Integrations](https://userguide.zappost.com/zap-integrations/zap-post-integrations), including installation and user guides.
* There is also a full [User Guide here](https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide)

#### What is the quality of the printing presses used?

We use the highest quality HP Indigo colour production grade printing presses for our Zaps. Not to get too geeky about it, this print tech has unmatched colour and ink capabilities, can print on a broad range of substrates in the digital print industry and deliver the highest speeds for high print quality. Most importantly this ensures your Zaps are in the hands of your customers quickly and to a high standard- reflecting your brand in the best possible way.


---

# 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://userguide.zappost.com/zap-post-web-app/faq/technical.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.