SMARTTILE · CARRIERAUTOMATE™ · VERIZON REPAIR APIBETA

Verizon repair tickets, opened over the wire

SmartTile's Verizon client is built to the VPS Exchange API v2.4 spec and wired into CarrierAutomate behind a SuperAdmin switch. Until Verizon authorises our user on their side, Joey opens every Verizon ticket by phone — the fallback is already the default.

SmartTile integrates with
Verizon VPS Exchange Repair API (GYEV, v2.4) — VzB and VzT service profiles — API key + 2-way SSL client certificate, UAT and production endpoints, plus Verizon's realtime-status webhook.
How SmartTile automates it
When a Verizon circuit is confirmed down, the API-first gate builds the trouble report from the device, site and contact and posts /addticket; any skip or failure is journalled and handed to Joey. BETA: no ticket has been opened over the API yet — Verizon's application layer still answers 401.
Category
CarrierCarrierAutomate™

Every Verizon trouble ticket SmartTile opens today is opened by Joey Circuits, our voice agent, working Verizon's IVR. The Verizon Repair API is the faster path: one authenticated POST instead of a phone call. SmartTile has the whole client built — payloads pinned to Verizon's v2.4 spec by a conformance test, a certificate-carrying HTTPS agent, a console, and a gate that decides API or phone per ticket. It is not in production yet: see the status box below.

What changes when the API path is switched on

The momentToday (Joey, live)With the API path (beta)
A Verizon circuit goes downJoey dials Verizon, navigates the IVR, relays the circuit ID and site contact, and reads back the ticket number.The gate posts /addticket with the service ID, site address, access contact and dispatch authorisation. No call is placed.
The API says no—The reason is written to the ticket journal and Joey takes the ticket (fallback switch, on by default). Every failed attempt counts as a strike; 10 strikes hands it to a live engineer.
Which Verizon is this?Joey is briefed on the circuit and service type.lineSearch asks Verizon for the service profile (VzB / VzT) and class before the ticket is built.
Status and notesJoey calls back on the follow-up cadence./addcomment, /modifyticket, /escalate and /cancelticket are built; realtime-status pushes are received and matched to the ticket.

How it is switched on

  1. Verizon issues SmartChoice the credentials: API key, CLE ID, user ID, ACNA and a 2WAYSSL client certificate for our CLE ID.
  2. SuperAdmin → Verizon API (/sa-verizon-api): enter the key, CLE ID, source system and default network ID; paste the certificate and private key (PEM).
  3. Pick UAT or production — blank base URL uses Verizon's published endpoint for that environment.
  4. Click Test connection. It calls lineSearch and tells apart an Akamai edge refusal, a gateway key rejection and Verizon's own "user is unauthorized".
  5. Turn on Use the API before calling. Leave Fall back to Joey on.
Switch (SuperAdmin)Default
Verizon API firstOff — Joey only
Fall back to Joey if the API failsOn
Verizon API kill switchOff (on = no API call at all)
Verizon integration enabledMaster switch for the client
Status, 2026-09-28: UAT, key and certificate accepted; Verizon's user registry rejects the user (HTTP 401) on every call. Verizon must map our certificate / CLE ID to an authorised user. The API-first switch is off; Joey handles Verizon.
SmartChoice · SmartTile CarrierAutomate™ — Verizon Repair APIPage 1 of 2
SMARTTILE · CARRIERAUTOMATE™ · VERIZON REPAIR API — WHAT VERIZON RECEIVES, AND HOW IT IS KEPT SAFE

What goes into a Verizon trouble report

The line

Service ID, VzB / VzT profile, network ID (the state code read from a VzT circuit ID, or your default), issue type mapped from the outage severity.

The site

Premises name and address, the on-site access person (name, phone, e-mail) and access hours, from the SmartTile device and location.

The authorisations

Dispatch = what the ticket says. Charges advised is sent only when billable dispatch was approved — never hard-coded.

Exactly what SmartTile calls (all POST, …/gyev-vpssa-ticket)

POST/addticketOpen the trouble report; our Rev.io ticket rides as customerRefNumber
POST/modifyticketUpdate an open ticket
POST/addcommentAdd a note; also stored on the SmartTile ticket
POST/escalateEscalate a ticket
POST/cancelticketCancel a ticket
READ/lineSearchService profile / class for a circuit; also the connection test
READ/getInventoryDetailsForCircuitCircuit inventory lookup
IN/api/webhooks/verizon/realtime-statusVerizon status push, Basic-Auth, matched by correlation ID

Security and control

Encrypted, never shown

API key, certificate, private key, passphrase and webhook secret are encrypted at rest; the console shows only that each is set, plus the certificate's subject and expiry.

Every call logged

Each request and response goes to the carrier API log with the API key redacted — SuperAdmins can open any call in the console.

SuperAdmin only

The Verizon console and its switches are superadmin-only. One SmartChoice credential serves managed customers, because Verizon issues it to SmartChoice as the wholesale customer.

Common questions

QuestionAnswer
Can I use this today?No — it is beta. Verizon tickets are opened by Joey by phone today, which is live and unchanged by this switch.
What if the API misbehaves after launch?The kill switch stops every Verizon API call at once; the fallback switch keeps Joey on every failed attempt.
Will a webhook with no password be accepted?No. Without a configured webhook secret the endpoint refuses pushes, unless a SuperAdmin explicitly allows it.
Built to Verizon's spec, waiting on Verizon's authorisation — and Joey opens the ticket in the meantime.
SmartChoice · smarttile.smartchoiceus.com · (800) 217-3096, 24×7 · verified 2026-09-28Page 2 of 2