# Mocking the Interface

## Introduction

OpenActive data has a large number of recommended and optional fields, some of which are not available from all providers.

Although it is always advisable to take a [defensive approach](https://github.com/imin-ltd/developer-docs/blob/dbd5919978c1377c987b09ba3888e183c32246ca/guides/defensive-data-consumption.md) due to this variance, in order to future-proof your interface, it can be useful to see all available fields in a single result item.

## Dummy Data: *Lorem Fitsum*

Our sandbox environment contains a data source called "*Lorem Fitsum*", which produces complete records of dummy data, based in the area of Oxford:

* **Address:** 🇬🇧 Oxford, Oxfordshire, England, United Kingdom
* **Latitude:** 51.7520131
* **Longitude:** -1.2578499

`loremfitsum` data contains two types of record with a rough 50/50 split across both:

* **Randomly generated:** these contain a random collection of OpenActive recommended and optional fields, but does not necessarily include all fields.<br>
* **Golden records:** these have a "GOLDEN:" prefix in their `name` property and contain all available fields in the OpenActive, OpenActive Beta, and imin [namespaces](https://docs.imin.co/using-the-platform/our-data/context-and-field-names). Note that other custom properties are available from data providers, documented in their `@context`, however, these are only present in the results endpoints (e.g. `/event-series/:id`) and not in the search summaries.

{% hint style="info" %}
Please see [Authentication](https://docs.imin.co/authentication#obtaining-an-api-key) for information on how to access our dummy data.
{% endhint %}