> ## Documentation Index
> Fetch the complete documentation index at: https://developer.plugsurfing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mirroring the Plugsurfing network in your system

OEM partners may want to maintain a local copy of the Plugsurfing charging network. This reduces the need to call the Drive API whenever a user interacts with the network or changes their position.

The local copy can include charging locations and the current availability status of individual charging stations and connectors (EVSEs).

## Recommended synchronization process

1. **Perform an initial full pull** Use **GeoSearch** to import the entire Plugsurfing network into your system by paginating through all locations.
2. **Keep the network up to date with delta pulls** Call **GetLocationsBatch** at regular intervals to retrieve only locations that have changed since the previous pull. Choose the interval based on how current the availability information needs to be for your intended user experience. The `last_updated` value is generated by Plugsurfing. Drive API consumers therefore do not need to account for incorrect or delayed timestamps provided by CPOs. Use the `last_updated` value of the last location in the last page as the starting point for next delta pull.
3. **Refresh the complete network weekly** We recommend performing a new full pull once a week. This ensures that your local copy remains consistent and allows you to remove locations that have been deleted from the Plugsurfing network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.