# Sales v2

import { Link } from "zudoku/components";
import { Card, CardDescription } from "zudoku/ui/Card";

:::lead
Entur's new and recommended interface for ticket sales in the Entur platform.
:::

## Access requirements

- [Partnership agreement with Entur (email us)](mailto:post@entur.org)
- [Client identification (ET-Client-Name)](/docs/getting-started#client-identification-et-client-name)
- [OAuth 2.0 authentication](/docs/authentication#partner-apis)

## What Sales v2 does

Sales v2 combines the main features of the Offers, Orders, Reserve Offers, Ticket Distribution, Refund, Seating Manager, Seatmap, Products, Customers, and NOD APIs. You no longer need to integrate with each of them separately.

Sales v2 takes over work that partners previously did themselves:

- **Search:** search directly with coordinates and addresses, without resolving place IDs first. Or search with the same `FareZone`, `StopPlace` and `TripPattern` references you are used to. Recommendations and bundling is configurable with useful defaults.
- **Purchase:** prepare a package with one or two calls. Add offers, additional products and more while the package is in draft, then proceed to payment whenever you are ready.
- **Tickets:** Sales v2 distributes and fetches travel documents on your behalf and rotates period tickets automatically. A single `GET` always returns the current travel documents. For now, we fetch NOD and PDF tickets on your behalf, but you would still need to integrate with Account-Based Ticketing separately.
- **Changes and cancellations:** move tickets, update validity window, refund customers and more. The API tells you which options are available for any given package.
- **Customers:** create and manage customers through the same API, with support for external references so you can keep a customer record in sync with your own. If you don't require customer profiles, you can still purchase anonymous travel documents and link them to customers in your own system.

## What Sales v2 does not cover

| You need | Use |
| --- | --- |
| Trip suggestions or place lookup in your own client | [Journey Planner](/docs/open-services/journey-planner) and [Geocoder](/docs/open-services/geocoder) |
| Receipts | [Receipt API](/apis/receipt-partner) |
| Third-party products | [Third Party Product API](/apis/third-party-product-partner) |
| Payment (optional) | Entur's [Payment API](/apis/payment-partner), or your own payment provider with imported payments. Sales v2 returns links to the payment endpoints you need. |
| Account-based ticketing with the ABT client libraries | [Account-based ticketing](/docs/partner-services/ticketing/account-based-ticketing) |
| Shared mobility, such as e-scooters and bikes | [Shared mobility](/docs/partner-services/sales-platform/shared-mobility) |
| The OSDM standard | Entur has a separate OSDM compatibility layer: [OSDM](/docs/partner-services/osdm) |

## About OMSA

Sales v2 is based on the Open Mobility Sales API (OMSA) specification.

## Next steps

<div className="grid grid-cols-1 md:grid-cols-2 gap-4 not-prose my-4">
  <Card className="p-6 gap-2 rounded">
    <p className="text-xs uppercase tracking-widest text-muted-foreground font-medium">Documentation</p>
    <Link to="/docs/partner-services/sales-v2/new-integration" className="text-base font-bold! underline text-foreground!">New sales integration</Link>
    <CardDescription>Building a sales integration with Entur for the first time? Understand the sales lifecycle and find the guides for your use case.</CardDescription>
  </Card>
  <Card className="p-6 gap-2 rounded">
    <p className="text-xs uppercase tracking-widest text-muted-foreground font-medium">Documentation</p>
    <Link to="/docs/partner-services/sales-v2/migrating-from-existing-sales-apis" className="text-base font-bold! underline text-foreground!">Migrating from Entur's existing sales APIs</Link>
    <CardDescription>Already selling through the Offers, Orders, Ticket Distribution, or Refund APIs? See where each step ends up in Sales v2.</CardDescription>
  </Card>
  <Card className="p-6 gap-2 rounded">
    <p className="text-xs uppercase tracking-widest text-muted-foreground font-medium">Guide</p>
    <Link to="/guides/sales-v2" className="text-base font-bold! underline text-foreground!">Sales v2 guides</Link>
    <CardDescription>Step-by-step instructions, from your first search to a confirmed purchase.</CardDescription>
  </Card>
  <Card className="p-6 gap-2 rounded">
    <p className="text-xs uppercase tracking-widest text-muted-foreground font-medium">API reference</p>
    <Link to="/apis/sales" className="text-base font-bold! underline text-foreground!">Sales v2 API reference</Link>
    <CardDescription>The full list of processes and collections.</CardDescription>
  </Card>
</div>
