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

# Roaming Offers Restrictions

Control which parts of your charging network are included in a roaming offer, and when it goes live. Useful when you want to roam selectively by country, by sub-network, or by OCPI party - with roaming partners, data aggregators or payment terminal providers alike - or to delay activation until a date that suits you.

### When to restrict

* You operate in multiple countries but only want to share specific markets.
* You run multiple sub-networks through separate OCPI parties and want some out of scope for this agreement.
* You've agreed to roam but don't want data and charging to go live until a specific date. For example, once commercial or administrative setup is complete.

<figure><img src="https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FRm7YyCiOLoDd0bdcs0kC%2Fimage.png?alt=media&amp;token=de72ca43-a29a-47b2-958e-40510bfb23ee" alt=""><figcaption></figcaption></figure>

### Country filter

During **Step 3: Configure the offer**, expand **Advanced settings**:

1. Select *Specific countries* instead of *All countries*.
2. Choose the countries to include.

### Party filter

In **Advanced settings**:

1. Select *Specific parties* instead of *All parties*.
2. Choose which of your parties to include.

### **Activation date**

Under "When would you like to begin roaming once the offer has been accepted?":

1. Leave Immediately selected to activate as soon as the contract is signed.
2. Select Specific date to choose a go-live date instead. Activation then happens on that date, or on signing, whichever comes later.

### What restrictions actually do

Restrictions affect what the partner **sees** — not what their drivers can physically do at a charge point.

* Drivers using the partner's app won't see or navigate to filtered stations.
* Drivers with an RFID card may still be able to charge at filtered stations by tapping directly, if tokens are allowed to whitelist at the charge point.

If you need to block authorizations entirely at certain stations, that's a charge point configuration — not a roaming offer restriction.


---

# 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.enapi.com/roaming/roaming-offers-restrictions.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.
