Get Experience Details

Fetches the details of a single experience.

This endpoint returns complete details about a single regular experience (events like concerts, parties, festivals, shows, etc.). Regular experiences are one-time or limited-duration events with specific start and end dates.

Note: This documentation covers regular experiences only (cinema: false). For cinema experiences (movies), see the Get Cinema Experience Details page.

Retrieve a Single Regular Experience

get

Fetch detailed information about a specific regular experience using the experience ID. Regular experiences are one-time or limited-duration events with specific start and end dates.

IMPORTANT: Always validate that the end_date has NOT passed before allowing customers to purchase tickets.

Path parameters
experience_idstring · uuidRequired

Unique identifier for the experience (UUID format)

Example: 223f279b-28b2-4b72-8020-cfc2c02b95cb
Responses
chevron-right
200

Successfully retrieved experience details

application/json
successbooleanOptional

Indicates whether the request was successful.

statusintegerOptional

HTTP status code (200 for success).

messagestringOptional

Human-readable description of the response.

get
/api/v1/merpi/experience/v/{experience_id}

Path Parameters

Parameter
Type
Required
Description

experience_id

string (UUID)

Yes

Unique identifier for the experience. Obtained from the list experiences endpoint.

Response Format

Root Response Object

Field
Type
Description

success

boolean

Indicates whether the request was successful.

status

integer

HTTP status code (200 for successful requests).

message

string

Human-readable description of the response.

data

object

Experience details object.

Data Object (Experience Details)

Field
Type
Description

id

string (UUID)

Unique identifier for the experience.

title

string

Name/title of the experience.

start_date

string

Start date and time of the experience in readable format ("Day, DD Mon YYYY HH:MM:SS").

end_date

string

End date and time of the experience in readable format ("Day, DD Mon YYYY HH:MM:SS").

description

string

Complete detailed description of the experience. May contain HTML or plain text.

featured

boolean

Indicates if the experience is featured on the platform.

cinema

boolean

Will always be false for regular experiences.

address

object

Complete venue location details.

image

array

Array of image objects. All promotional images for the experience.

business

object

Information about the business/organizer hosting the experience.

category

object

Category classification of the experience.

created_on

string

Timestamp when the experience was created in readable format ("Day, DD Mon YYYY HH:MM:SS").

Address Object

Field
Type
Description

street

string

Street address of the venue.

town

string

Town or locality.

city

string

City where the experience takes place.

country

string

Country name (typically "Nigeria").

Image Object

Field
Type
Description

image

string (URL)

Full HTTPS URL to the experience image.

Business Object

Field
Type
Description

id

string (UUID)

Unique identifier for the business.

name

string

Business/organizer name.

photo

string (URL) / null

URL to the business profile photo. May be null if no photo uploaded.

slug

string

URL-friendly identifier for the business.

type

string

Type of business (e.g., "entertainment").

Category Object

Field
Type
Description

id

string (UUID)

Unique identifier for the category.

slug

string

URL-friendly identifier for the category.

name

string

Display name of the category (e.g., "Parties", "Concerts", "Festivals").

Request Examples

Basic request

Using cURL

Using JavaScript (Fetch)

Using Python (Requests)

Validating Experience Availability

circle-exclamation

Always validate that the experience end_date has NOT passed before allowing customers to purchase tickets. Selling tickets for expired events results in poor customer experience and potential refund issues.

Implementation requirement:

  • Compare current date/time with end_date

  • If current time > end_date, the experience has ended

  • Block ticket purchases and display "Event has ended" message

  • Consider hiding or marking expired experiences in listings {% endhint %}

JavaScript Validation Example

Python Validation Example

Complete Validation with Start Date

Understanding Date Formats

This endpoint returns dates in a human-readable format rather than ISO 8601:

Format: "Day, DD Mon YYYY HH:MM:SS"

Examples:

  • "Wed, 29 Jan 2025 04:41:00"

  • "Sat, 15 Dec 2024 18:30:00"

Parsing Dates in Your Application

JavaScript

Python

Common Use Cases

Display Event Details Page

Filtering Out Expired Events

Key Differences from Cinema Experiences

Regular experiences differ from cinema experiences in the following ways:

Feature
Regular Experience
Cinema Experience

cinema field

Always false

Always true

cinema_info object

Not present

Present with showing and times

Duration

Fixed start and end dates

Recurring showtimes

Ticket types

Event-based

Showtime-based

Booking flow

Book for entire event period

Select specific showtime

circle-exclamation

Next Steps

After fetching experience details, you can:

  1. Validate availability - Check if end_date has passed before allowing purchases

  2. Get ticket types and pricing - Use the tickets endpoint with the experience_id

  3. Book tickets - Use the booking endpoint to reserve tickets (only if event hasn't ended)

  4. Share experience - Use the slug from business object to create shareable links

  5. Get directions - Use the address object to integrate with maps services

  • Get List of Experiences - Browse all experiences with filtering

  • Get Ticket Types - Fetch available ticket types for this experience

  • Create Booking - Book tickets for this experience

  • Get Cinema Experience Details - For cinema-specific experiences

Last updated