Get single service by ID

Retrieve the details of a specific service using its unique service ID (UUID). This endpoint is useful for fetching details when displaying service information, processing transactions, or managing price data for individual items in your application.

Requirements

• id (service ID) is required.

Usage

Request

• Method: GET
• Path: /services/{id}

Path Parameters

| Name | Type | Required | Example | Description | |------|--------|----------|---------|-------------| | id | string | Yes | 3fa85f64-5717-4562-b3fc-2c963f66afa6 | Unique service ID (UUID). |

Example

curl -X GET "https://api.example.com/services/3fa85f64-5717-4562-b3fc-2c963f66afa6"

Response

200 OK

Returns a standard API envelope with the service details in data.

Example:

{
  "status": true,
  "path": "string",
  "statusCode": 0,
  "message": "string",
  "data": {
    "id": "string",
    "status": "string",
    "service_title": "string",
    "slug": 0,
    "service_category_id": 0,
    "service_subcategory_id": "string",
    "search_tags": "string",
    "service_description": "string",
    "current_step": "Unknown Type: string,null",
    "basic_package_title": "Unknown Type: string,null",
    "standard_package_title": "Unknown Type: string,null",
    "premium_package_title": "string",
    "basic_package_description": "Unknown Type: string,null",
    "standard_package_description": "string",
    "premium_package_description": "string",
    "premium_short_description": "Unknown Type: string,null",
    "basic_attributes": [
      {
        "key": "string",
        "value": true
      }
    ],
    "standard_attributes": [
      {
        "key": "string",
        "value": true
      }
    ],
    "premium_attributes": [
      {
        "key": "string",
        "value": true
      }
    ],
    "basic_price": 0,
    "standard_price": 0,
    "premium_price": 0,
    "basic_delivery_time": 0,
    "standard_delivery_time": 0,
    "premium_delivery_time": 0,
    "is_offer_packages": true,
    "is_featured": true,
    "is_best_seller": true,
    "user_meta": {
      "first_name": "string",
      "last_name": "string",
      "user_name": "string",
      "email": "string",
      "date_of_birth": "string",
      "about_me": "string",
      "gender": "Unknown Type: string,null",
      "profile_image": "string",
      "join_as": "string",
      "user_status": "string",
      "created_at": "string",
      "updated_at": "string",
      "inactive_till": "string",
      "is_forever_inactive": true,
      "is_push_active": true,
      "is_seller": true,
      "city": "string",
      "country": "string",
      "zone": "string",
      "zip_code": "string",
      "location": "string",
      "avg_rating": 0,
      "total_reviews": 0,
      "member_since": "string",
      "last_active": "string",
      "profile_completion": 0,
      "seller_info": {},
      "sub": "string",
      "total_items": 0,
      "total_sales": 0
    },
    "thumbnail_image_id": 0,
    "thumbnail_video_id": "Unknown Type: number,null",
    "created_by": "string",
    "updated_by": "string",
    "created_at": "string",
    "updated_at": "string",
    "total_views": 0,
    "total_sales": 0,
    "total_reviews": 0,
    "avg_rating": "string",
    "total_share": 0,
    "total_likes": 0
  }
}

Notes

• The response uses a standard envelope: status, path, statusCode, message, and data.
• Package fields and some fields are returned as "Unknown Type: string,null" in the schema; treat them as nullable strings in your implementation.
• Attribute arrays (basic_attributes, standard_attributes, premium_attributes) contain key/value pairs where value is a boolean.
• user_meta includes seller/user information associated with the service.