Customers
Store customer profile information for use in the sales platform.
Some of Entur's services require that the customer is registered in Entur's customer database and has a . The profiles API is used to create and manage customers in the Entur system. It offers a variety of different fields that can be set, but most are optional.
Customer profiles are not shared between organisations.
Organisations can also give profiles their own .
Permanent profiles
A permanent profile is a profile for a customer that is registered and using the same profile for buying tickets. See the profiles client in the profiles API
Temporary profiles
Temporary profiles can be used to allow anonymous purchasing of tickets. These profiles require an expiration date, usually set to a time after the journey is completed. A temporary profile cannot be reused, but it can be converted to a permanent profile in case the customer decides to register after the purchase. If the customer already has a permanent profile, the temporary profile can be merged with the permanent profile using the connect profile to permanent profile endpoint.
See the temporary profiles client in the profiles API
Preferences
The preferences API allows you to define preferences for your organisation and add these preferences to the customer's profile. Examples of preferences can be preferred user type when purchasing tickets, whether they are using a wheelchair or other types of assistance, et cetera. It is up to your organisation how you use this data.
See the preferences client in the profiles API
Customer accounts
The connection between a customer profile and the customer account when using the Account Based Ticketing Solution is maintained in the profiles client. A customer can have multiple customer accounts.
See the customer accounts client in the profiles API
Deleting profiles
To delete a profile you have to deactivate the customer. An expiration date is required in the request, which is the date when the profile is deleted from the database. The profile cannot be used after the deactivation is done, but it is recoverable until deletion. We recommend that this date is set to 2-3 days in the future, in case the customer deletes its profile by accident.
When a customer is deactivated, a Kafka event is produced. This event triggers deletion of data connected to the profile in Entur's system.
See the deactivate customer documentation and restore deactivated customers documentation
Kafka events
Whenever a change is made to customer profiles for your organisation. This includes creations, updates, and deletions of profiles.
Contact us at team.personalisering@entur.org to subscribe to these topics.
Topic names for production:
- customer-changed-production-[organisation ID]