# Service Specification (Info)
Service specification information is included as part of other requests (e.g., appointments, orders, service availability).
# Where is serviceSpecification Used?
- Order Management: Required in all provide orders.
- Appointment Management: Required for booking appointments.
- Service Availability: Returned in available services.
# Field Requirements
The serviceSpecification object typically includes:
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | Unique identifier for the service type (e.g., fttp) |
| name | string | No | Human-readable name (e.g., FTTP) |
Refer to the relevant API section for field-level requirements and example payloads.
# Example Usage
The serviceSpecification object is used in appointment and order requests:
"serviceSpecification": {
"id": "fttp",
"name": "FTTP"
}
# Common Service Specification IDs and Names
| ID | Name | Description |
|---|---|---|
| fttp | FTTP | Fibre to the Premises |
| ftthl2r | FTTH Layer 2 Relay | Layer 2 relay service |
| ... | ... | (Contact your account manager for a full list) |
If new endpoints for products or service specifications are added in the future, they will be documented here.