Get your Texas811 tickets and responses through an API

What you can build on the Texas811 Portal

• Get your company's tickets

  Build this

  Runs a Ticket Search with My Company Tickets and a date range, and reads each ticket in the results dashboard.

  Takes

  Start date, end date (at most 31 days apart)

  Returns

  Ticket number, ticket type, creation date, work on date, county, city, street, excavator, caller

• Check a ticket's positive responses

  Build this

  Opens a ticket, selects View Responses and reads each utility member's line in the Positive Response panel.

  Takes

  Ticket number

  Returns

  Utility member, responded or not, response type, response date and time, comments

• Read a ticket's history

  Build this

  Opens a ticket's History and reads every action logged on it.

  Takes

  Ticket number

  Returns

  Ticket number, creation date, actions with date, time and description, days since creation

• Submit an Update or Update/Remark ticket

  Build this

  From a ticket's details, selects Create, then Update, picks Update or Update/Remark and submits it.

  Takes

  Ticket number, Update or Update/Remark

  Returns

  New ticket number, ticket type, work on date

Automate the Texas811 Portal with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Missing positive responses, before the crews leave

  Build this

  Starts

  Every weekday at 6:30, Central Time

  Step 1

  Get your company's tickets created in the last 10 days.

  Step 2

  For each ticket, check its positive responses.

  Step 3

  Keep the utility members with no response yet or a response of In Conflict.

  Step 4

  Email you the list, one section per ticket with its street and work on date.

• Tickets nearing 30 days, listed for an Update decision

  Build this

  Starts

  Every weekday at 7:00, Central Time

  Step 1

  Get your company's tickets created 24 to 29 days ago.

  Step 2

  For each ticket, read its history.

  Step 3

  Email you the list, so someone decides which jobs need an Update or Update/Remark.

• Weekly ticket report to your job system

  Build this

  Starts

  Every Monday at 8:00, Central Time

  Step 1

  Get your company's tickets created in the last 7 days.

  Step 2

  For each ticket, check its positive responses.

  Step 3

  Post each ticket with its responses to your job costing or ERP webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get your company's tickets” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "txgc.texas811.org/get_company_tickets",
    "input": {
      "start_date": "2026-11-02",
      "end_date": "2026-11-11"
    }
  }'

{
  "status": "completed",
  "data": {
    "company": "Acme Underground LLC",
    "tickets": [
      {
        "ticket_number": "7310045118",
        "ticket_type": "Normal",
        "created": "2026-11-10T14:22:00-06:00",
        "work_on": "2026-11-12T14:30:00-06:00",
        "county": "Travis",
        "city": "Austin",
        "street": "4100 Northwind Dr",
        "excavator": "Acme Underground LLC",
        "caller": "Field Office 2"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

The Texas811 Portal’s own options

The Texas811 help centre describes no API or data feed for excavators. You work in the Portal itself, a GeoCall site. Ticket Search exports its results to Excel or CSV, a ticket can be sent by email from the dashboard's ticket actions, and Print with Positive Response puts the members' responses on the printout.

Read on November 12, 2026: Viewing and Managing Search Results, Ticket Actions from the Dashboard, Performing Ticket Searches.

Signing in to the Texas811 Portal

The Texas811 Portal signs you in with a username, which is the email address you signed up with, and a password, with a Remember Me option. Each account belongs to one person. With Fous you sign in once through the Portal's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

One account per person, one company name

Accounts are for individual use, and the username and caller's name cannot be changed. My Company Tickets matches the company name in Excavator Details exactly, so everyone should spell it the same way.

31 days per search, 14 tickets per page

A Ticket Search covers at most 31 days and reaches back 4 full calendar years. The results dashboard shows 14 tickets per page, so a longer period means several searches.

Update within 30 days

An Update or Update/Remark is only possible while the most recent ticket is within 30 days. After that a new ticket is needed. Both are sent with a two-business-day notice.

Green does not always mean marked

Open responses 5 or more days old are closed by the system once 48 hours have passed since the Work On date. Such a ticket shows green, so read the response type and history, not just the colour.

More in Government: US courts, records, permits and licensing

• Sunshine 811
• USA North 811
• Accela Citizen Access
• DOB NOW
• Metrc
• webDEALER
• The Compliance Engine
• eFileIL
• eFileTexas
• Florida Courts E-Filing Portal
• Odyssey File & Serve
• LOOP

Other industries: Mercury Network, FINRA Gateway, AASHTOWare Project Civil Rights & Labor, MyFTB, SOSPortal, MISUMI.