# Authentication
Source: https://docs.wander-app.fr/api-reference/authentication

How to access API endpoints ?

All API endpoints, with the exception of the `/login` endpoint, are authenticated using Bearer tokens.
To obtain a Bearer token, you need to authenticate yourself with a `clientId` and a `clientSecret` using the `/login` endpoint.

<Card title="Request credentials from the Wander team" icon="hand" href="mailto:contact@wander-app.fr">
  To use Wander API endpoints, you need a Wander account. Send a mail to [contact@wander-app.fr](mailto:contact@wander-app.fr)
</Card>


# Get clicks
Source: https://docs.wander-app.fr/api-reference/client-data/get-clicks

api-reference/openapi.json get /v2/clicks



# Login
Source: https://docs.wander-app.fr/api-reference/clients-login/login

api-reference/openapi.json post /login
It generates a refreshToken valid for 7 days to relogin and an accessToken valid for 1 hour to use the next endpoints.



# Dynamic search
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/dynamic-search

api-reference/openapi.json get /v2/search
Search for event or place or performer. You can use it for a searchbar.



# Get event
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/get-event

api-reference/openapi.json get /v2/event/{eventId}
Get event's whole informations. You can use it to create a page for the event.



# Get events
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/get-events

api-reference/openapi.json post /v2/get/events
Get events according to your filters. You can use it to serve a map or event stream.



# Get performer events
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/get-performer-events

api-reference/openapi.json get /v2/performer/{performerId}
Get performer's whole informations and the events in which they take part. You can use it to create a page for the performer.



# Get place events
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/get-place-events

api-reference/openapi.json get /v2/g-place/{googlePlaceId}
Fetch detailed information about a Google Place, including scheduled events.



# Search performer events
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/search-performer-events

api-reference/openapi.json get /v2/search/performer
Search for a performer by name. A not-null result will only be returned if the performer's identity can be confidently confirmed and if at least one of their events is already recorded in our database.



# Search place events
Source: https://docs.wander-app.fr/api-reference/direct-event-data-serving/search-place-events

api-reference/openapi.json get /v2/search/place
Search for a place by name. A not-null result will only be returned if at least one event has already taken place at this place in our database.



# Get events catalogue
Source: https://docs.wander-app.fr/api-reference/event-data-fetching-and-storage/get-events-catalogue

api-reference/openapi.json post /v2/get/catalogue
Get and store all events. You can use it to keep your database up to date.



# Create your event stream
Source: https://docs.wander-app.fr/api-reference/event-stream

This page explains how to use the [get events](/api-reference/direct-event-data-serving/get-events) endpoint to create an event stream or an event map.

<Steps>
  <Step title="Define your filters">
    **Customize your event stream or map** by specifying the types of events you want to see.

    For instance:

    * **music** and **performance** events: `categories` = **\['musique', 'spectacle']**
    * events from **Shotgun** and **Dice**: `sources` = **\['dice', 'shotgun']**
    * events in paris:
      * `locationFilter.circle.lat` = **48.864716**
      * `locationFilter.circle.lng` = **2.349014**
      * `locationFilter.circle.maxDistance` = **10000**
    * events taking place next week:
      * `datesFilter.minDate` = **2025-01-01T08:00:00.000Z**
      * `datesFilter.maxDate` = **2025-01-07T23:00:00.000Z**
    * free events:
      * `pricesFilter.lowestPrice` = **0**
      * `pricesFilter.highestPrice` = **0**
    * ...
  </Step>

  <Step title="Use the results">
    Use `data` to show events in your stream or map.

    You can see the number of events corresponding to your filters in `pagination.totalItems`.
    If you want to show more than the `limit` number of events, you can increment `pageNumber` as long as it is less than `totalPages`.

    Information about the partners selling the event are available in `data.sources`.
    <Tip>You can use the `data.sources.link` to redirect your users to the site of the partner selling the event and generate sales.</Tip>
  </Step>
</Steps>


# FAQ
Source: https://docs.wander-app.fr/api-reference/faq



<AccordionGroup>
  <Accordion title="How to have my credentials ?" icon="key">
    Contact us at [contact@wander-app.fr](mailto:contact@wander-app.fr)
  </Accordion>

  <Accordion title="How to find an event ?" icon="calendar-days">
    You can use the [dynamic search](/api-reference/direct-event-data-serving/dynamic-search) endpoint specifying `reponseFilter`=`events`.
  </Accordion>

  <Accordion title="How to find an artist's events ?" icon="palette">
    You can use the [search performer events](/api-reference/direct-event-data-serving/search-performer-events) endpoint.

    It will return a not-null response only if at least one of the artist's events is or was present in our database.
  </Accordion>

  <Accordion title="How to find a place's events ?" icon="building">
    You can use the [search place events](/api-reference/direct-event-data-serving/search-place-events) endpoint.

    It will return a not-null response only if we have already had an event at that place in our database.
  </Accordion>
</AccordionGroup>


# Introduction
Source: https://docs.wander-app.fr/api-reference/introduction

Overview of Wander API usage modes and available endpoints

## Welcome

Wander's API provides two modes of event data interaction: **Direct Event Data Serving** and **Event Data Fetching and Storage**. Depending on your needs, you can either retrieve data in real-time without storing it or fetch and store data for later use.

### Direct Event Data Serving

In this mode, you retrieve event data on demand, without storing it. This is ideal for applications needing live event data.

#### Available Endpoints:

* [Get events](/api-reference/direct-event-data-serving/get-events): Retrieve events based on filters (e.g., location, date, type). Perfect for populating a live event feed or map.

* [Get event](/api-reference/direct-event-data-serving/get-event): Fetch detailed data for a specific event, useful for creating individual event pages.

* [Dynamic search](/api-reference/direct-event-data-serving/dynamic-search): Implement a search bar to find events, places, or performers.

* [Get place events](/api-reference/direct-event-data-serving/get-place-events): Fetch detailed information about a Google Place, including scheduled events.

* [Search place events](/api-reference/direct-event-data-serving/search-place-events): Search for events in a place by name.

* [Get performer events](/api-reference/direct-event-data-serving/get-performer-events): Get performer’s whole informations and the events in which they take part.

* [Search performer events](/api-reference/direct-event-data-serving/search-performer-events): Search for events by performer name.

### Event Data Fetching and Storage

This mode is suitable when you need to store event data for further use and keep it updated.

#### Available Endpoint:

* [Get events catalogue](/api-reference/event-data-fetching-and-storage/get-events-catalogue): Retrieve all events and store them. You can also update existing data by specifying the date when the data was last fetched.


# Create and maintain your database
Source: https://docs.wander-app.fr/api-reference/storage

This page explains how to use the [get events catalogue](/api-reference/event-data-fetching-and-storage/get-events-catalogue) endpoint to create and maintain your own event database.

## Initial database synchronisation

<Steps>
  <Step title="Fetch all upcoming events">
    Use the [get events catalogue](/api-reference/event-data-fetching-and-storage/get-events-catalogue) endpoint without the `lastUpdatedAt` parameter to retrieve **all upcoming events**.

    You can't get all the events at once. To retrieve all events, make multiple requests by incrementing the `pageNumber` parameter until it exceeds the total number of pages indicated in `pagination.totalPages`.
  </Step>

  <Step title="Store them">
    Store the event details found in `data.events` in your own database.

    Make sure to save the event `id` returned for each event to identify them for future updates.
  </Step>
</Steps>

## Database maintenance

<Steps>
  <Step title="Retrieve updates since your last sync">
    Set the `lastUpdatedAt` parameter to the timestamp of your **last successful synchronisation**.
    <Warning>This timestamp should reflect the **start date** of your last update.</Warning>
    Again, increment the `pageNumber` parameter to retrieve all updates.
    <Tip>Availabilities are checked **every 20 minutes**. Major updates are released at **10am**.</Tip>
  </Step>

  <Step title="Store changes">
    This will retrieve all event details, including unchanged ones, for events that have been **modified since your last sync**.

    You can choose to either completely **replace** the existing **event information** with the new data or **update the fields** individually by checking for changes.
  </Step>

  <Step title="Update deleted events">
    You will also receive an array of event ids in `eventIdsDeleted` for events removed due to duplicates identified since your last sync.
    To keep your database up to date, **delete the events matching these ids**.
    <Note>You can identify the events with which these have been merged by checking the `sources` `id`s.
    For example, if you've stored interactions with these events, you can transfer them to the newly merged events.</Note>
  </Step>
</Steps>

## Major update times

1. **10am** : up to 10 000 events at once, including overnight updates and integrations.
2. 2pm : up to 1000 events
3. 6pm : up to 1000 events
4. 10pm : up to 1000 events

<Note>Event availabilities are updates every 20 minutes.</Note>

## Best practices

...


# The event distribution hub
Source: https://docs.wander-app.fr/event-data-hub

Access a wide range of monetised events and cultural activities.

## Introduction

Wander serves as a **real-time event distribution hub** that consolidates events from **numerous ticketing partners** and makes them accessible through an **API**.

The platform centralizes information on a diverse array of events, including **concerts**, **shows**, and **exhibitions**, sourced from providers such as **FnacSpectacles**, **Ticketmaster**, **Fever**, and many others.

Wander offers **businesses** and **developers** straightforward access to these events through its API, enabling them to integrate events into their **own applications** or **systems**.

Finally, Wander facilitates **earnings** for its partners by granting them a **commission** on every ticket sale, establishing a collaborative revenue-sharing model.
This method empowers our clients to utilize **up-to-date event informations** and benefit from its **financial opportunities**.

## Our benefits

<CardGroup>
  <Card title="Instant access to a broad selection of events available" icon="calendar-days" href="https://wander-app.fr/explore">
    Over **65,000 events** across France and Europe, spanning more than **20 categories** including shows, concerts, exhibitions, and flea markets.
  </Card>

  <Card title="Generate additional income" icon="dollar-sign">
    Thanks to our collaborations with over **20 ticketing partners**, you earn a commission ranging from **1% to 15%** of the ticket price on every sale.
  </Card>
</CardGroup>

## Our services

<CardGroup>
  <Card title="API access" icon="gear" href="/api-reference/introduction">
    Easy API integration for live use of event data
  </Card>

  <Card title="Partnerships negotiation" icon="dollar-sign">
    We negotiate with ticketing companies to provide our partners with the best commission levels
  </Card>

  <Card title="Back office access" icon="browser" href="https://wander-app.fr/office">
    Monitor your performance and easily visualize our whole range of events
  </Card>

  <Card title="Support" icon="slack">
    We address all your questions about integrating our API through a dedicated Slack channel
  </Card>
</CardGroup>