> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Get a port-in request's status timeline > Expand a port-in request's flat status into a six-stage timeline (submitted, validating LoA, carrier review, FOC assigned, FOC scheduled, completed) with per-stage state and timestamps, the elapsed-days counter, the FOC date once assigned, and — on rejection — a plain-English explanation of the carrier's reject code plus a recommended action. Pure read: it transforms the request you already have and makes no carrier call. Requires the `numbers:read` scope. ## OpenAPI ````yaml /openapi.yaml get /api/v1/numbers/porting/{id}/timeline openapi: 3.1.0 info: title: Devotel CPaaS API description: Orbit by Devotel — Communications Platform as a Service API version: 1.0.0 contact: name: Devotel url: https://devotel.io email: support@devotel.io license: name: Proprietary servers: - url: https://api.orbit.devotel.io description: Production security: - Bearer: [] - ApiKey: [] tags: - name: Messages description: >- Send and manage messages across all channels (SMS, WhatsApp, RCS, Email, Viber, etc.) - name: Fax description: >- List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers (sending flows through the Messaging API) - name: Agents description: AI agent creation, configuration, and execution - name: Voice description: Voice calls, IVR, conferencing, and SIP trunking - name: OnCall description: On-call rotations and escalation policy planning for incident alerting - name: Webhooks description: Webhook endpoint management and delivery logs - name: Numbers description: Phone number search, provisioning, and configuration - name: Brand Identity description: >- Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp, RCS, branded calling, number KYC) - name: Contacts description: Contact management, segmentation, and lifecycle tracking - name: Campaigns description: Marketing campaign orchestration and analytics - name: Flows description: Automation flow builder and execution engine - name: Templates description: Message template management and approval workflows - name: Settings description: Organization, channel, and user preference settings - name: Verify description: OTP generation and verification across channels - name: Push description: Push notification delivery via FCM and APNs - name: Integrations description: Third-party service connections and OAuth management - name: CDP description: >- Customer Data Platform — activation surface (CRM object sync, streaming destinations, ad-audience activation) - name: Files description: >- Server-to-server media upload, listing, retrieval, and deletion (signed-URL backed) - name: Commerce description: >- Omnichannel conversational-commerce — persistent cart + checkout state machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout, and AP2-style agent payment mandates. - name: Sync description: >- Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps, Lists, and ephemeral Streams, with change events relayed over the /api/v1/ws/sync WebSocket gateway - name: Risk description: >- Unified cross-channel Trust & Fraud risk scoring — fuses SMS-pumping, URL-reputation, Verify Fraud Guard, and Voice Biometrics signals into one composite verdict queryable before a send or a call. - name: Orby description: >- In-dashboard Orby operator assistant: streamed assistant turns, conversation threads, product knowledge-base search, and the tool-action approval gate. Available to signed-in operators only (dashboard session auth — API-key requests are rejected). paths: /api/v1/numbers/porting/{id}/timeline: get: tags: - Numbers summary: Get a port-in request's status timeline description: >- Expand a port-in request's flat status into a six-stage timeline (submitted, validating LoA, carrier review, FOC assigned, FOC scheduled, completed) with per-stage state and timestamps, the elapsed-days counter, the FOC date once assigned, and — on rejection — a plain-English explanation of the carrier's reject code plus a recommended action. Pure read: it transforms the request you already have and makes no carrier call. Requires the `numbers:read` scope. parameters: - schema: type: string in: path name: id required: true description: The port-in request id. responses: '200': description: The staged timeline for the port-in request. content: application/json: schema: type: object properties: data: type: object properties: portingId: type: string status: type: string enum: - submitted - reviewing - approved - completed - rejected - supplement_submitted elapsedDays: type: integer description: Calendar days elapsed since the request was submitted. focDate: type: string format: date-time nullable: true stages: type: array items: type: object properties: stage: type: string enum: - submitted - validating_loa - carrier_review - foc_assigned - foc_scheduled - completed enteredAt: type: string format: date-time nullable: true state: type: string enum: - current - completed - pending - skipped label: type: string detail: type: string rejection: type: object nullable: true description: >- Structured explanation of the carrier reject code, present only when status is `rejected`. properties: code: type: string summary: type: string recommendedAction: type: string severity: type: string meta: $ref: '#/components/schemas/ResponseMeta' example: data: portingId: port_01J9Z8ABCDEF status: reviewing elapsedDays: 3 focDate: null stages: - stage: submitted enteredAt: '2026-08-11T09:30:00Z' state: completed label: Submitted - stage: validating_loa enteredAt: '2026-08-11T10:05:00Z' state: completed label: Validating LoA - stage: carrier_review enteredAt: '2026-08-12T08:00:00Z' state: current label: Losing carrier review detail: 'Expected: 5 days, elapsed: 3 days' - stage: foc_assigned enteredAt: null state: pending label: FOC date assigned - stage: foc_scheduled enteredAt: null state: pending label: Scheduled for FOC - stage: completed enteredAt: null state: pending label: Port complete meta: request_id: req_01J9Z8ABCDEF timestamp: '2026-08-14T12:00:00Z' components: schemas: ResponseMeta: type: object required: - request_id - timestamp additionalProperties: false properties: request_id: type: string description: Unique request identifier (also returned as X-Request-Id header) timestamp: type: string format: date-time docs_url: type: string format: uri nullable: true securitySchemes: Bearer: type: http scheme: bearer bearerFormat: JWT description: Dashboard JWT token from Clerk ApiKey: type: apiKey name: X-API-Key in: header description: Server-to-server API key (dv_live_sk_*) ````