This topic introduces the Episerver Profile Store API, used for querying, creating, and updating visitor profiles, segments, and scopes. The Profile Store API is separated from the Tracking API so that it has independent processing loads.
Note: Episerver ships the API with Swagger documentation. Append /swagger to the root URL to access swagger documentation and test functionality. However, not all APIs are available for testing in production.
Tracking is based on the following concepts:
You can use HttpClient or a third-party REST client combined with a JSON library, to make calls to the Profile Store API.
Use the Authorization header for authentication with a value in the following format: epi-single key; it contains the subscription key that is passed to the API with each request.
Last updated: Sep 14, 2018