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

# Arketa

Use Arketa reservation, purchase and referral data in your Perkville program.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

* **Reservations** — Reward eligible event activity.
* **Purchases** — Award a flat amount for an item or item type, including qualifying membership/package purchases.
* **Referrals** — Referral information can be imported from Arketa.

{% hint style="warning" %}

* **Limitations** — The listed integration does not include pre-booking rewards, refund deductions or automatic redemptions.
  {% endhint %}

Your configured rules determine which eligible activities award points and which workflows are enabled.

## Authentication

{% stepper %}
{% step %}

### Request whitelisting

To integrate Arketa and Perkville reach out to your Arketa representative and request whitelisting with Perkville.
{% endstep %}

{% step %}

### Work with Perkville to connect your Arketa instance

Once whitelisted, communicate with your Perkville representative to connect Arketa.
{% endstep %}
{% endstepper %}

## FAQ

### Are purchases rewarded by dollars spent?

The listed capability awards a flat amount by purchased item or item type. Confirm your intended rule with your CSR.

See the [Arketa partner profile](https://partners.perkville.com/partners/arketa) for additional integration information.


---

# 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.perkville.com/integrations/integration-reference/arketa.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.
