> ## 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. # Sign a port-in Letter of Authorization > Capture an in-platform signature on an uploaded LoA: record the authorized signer's name and email plus the verbatim acknowledgement text they agreed to, and move the signature state to `signed`. The request must already have a LoA in `draft` state; signing again returns 422. Requires the `numbers:write` scope. ## OpenAPI ````yaml /openapi.yaml post /api/v1/numbers/porting/{id}/loa/sign 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}/loa/sign: post: tags: - Numbers summary: Sign a port-in Letter of Authorization description: >- Capture an in-platform signature on an uploaded LoA: record the authorized signer's name and email plus the verbatim acknowledgement text they agreed to, and move the signature state to `signed`. The request must already have a LoA in `draft` state; signing again returns 422. Requires the `numbers:write` scope. parameters: - schema: type: string in: path name: id required: true description: The port-in request id. requestBody: required: true content: application/json: schema: type: object required: - signerName - signerEmail - acknowledgement properties: signerName: type: string description: >- Authorized signer's full legal name, matching the losing carrier's account. signerEmail: type: string format: email acknowledgement: type: string description: >- Verbatim acknowledgement text the signer agreed to (stored for legal reconciliation). example: signerName: Jane Roe signerEmail: jane.roe@acme.example acknowledgement: >- I certify that I am authorized to request the port of these numbers and that the details provided are accurate. responses: '200': description: The port-in request with signature state = signed. content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/PortingRequest' meta: $ref: '#/components/schemas/ResponseMeta' components: schemas: PortingRequest: type: object description: A number port-in request stored for the organization. properties: id: type: string numbers: type: array items: type: string currentCarrier: type: string status: type: string enum: - submitted - reviewing - approved - completed - rejected - supplement_submitted description: Carrier-side lifecycle state of the port-in. submittedAt: type: string format: date-time country: type: string nullable: true provider: type: string enum: - telnyx - didww - manual nullable: true description: Which DID provider the carrier-side order lives on, if any. providerOrderId: type: string nullable: true focDate: type: string format: date-time nullable: true description: >- Firm Order Confirmation date, when the carrier has scheduled the port. rejectionReason: type: string nullable: true requiresManualReview: type: boolean nullable: true description: >- True when the row exists only locally because carrier dispatch did not happen (manual mode). loaFileUrl: type: string nullable: true 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_*) ````