--- title: "Connect Docparser to DistrictAPI - APIANT.ai" description: "When \"Parsed Document Data Available\" fires in Docparser, your agent runs \"Batch lookup districts\" in DistrictAPI." canonical: "https://apiant.ai/connect/docparser-to-districtapi" --- # Connect Docparser to DistrictAPI When **Parsed Document Data Available** fires in [Docparser](https://apiant.ai/connections/docparser), your agent runs **Batch lookup districts** in [DistrictAPI](https://apiant.ai/connections/districtapi). Describe the whole flow and it is built, tested on every scenario and kept running. Docparser **2** triggers Docparser **2** actions DistrictAPI **8** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Docparser and DistrictAPI to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Docparser can start in DistrictAPI - When **Parsed Document Data Available** in Docparser then **Batch lookup districts** in DistrictAPI - When **Parsed Table Row Available** in Docparser then **Find districts by name, state or county** in DistrictAPI Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Docparser and DistrictAPI ## Triggers and actions 2 triggers · 10 actions - Trigger **Parsed Document Data Available** Triggers whenever a new Document is processed and parsed data is available. - Trigger **Parsed Table Row Available** Triggers whenever a new Document is processed and parsed table rows are available. - Action **Fetch Document From URL** Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - Action **Upload Document** Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - Action **Batch lookup districts** Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one. - Action **Find districts by name, state or county** Returns the school districts matching the name, state or county you supply. - Action **Get district** Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary. - Action **Get school** Returns the full profile of one school, including its address, grades served, enrollment and parent district. - Action **Get school's district** Returns the full profile of the school district a given school belongs to. - Action **List districts** Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID. - Action **List schools** Returns the schools near a street address or a pair of coordinates, within the radius you choose. - Action **List schools by district** Returns the open schools inside a given school district, optionally limited to one school type or to charter schools. ## Each app on its own - [ **Docparser** Docparser converts your PDF documents into structured and easy-to-handle data.](https://apiant.ai/connections/docparser) - [ **DistrictAPI** US school districts and schools by address, with enrollment and boundaries](https://apiant.ai/connections/districtapi) Reviews ## What our customers say ## More from Docparser - [ **Docparser to Prismix** Real-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required](https://apiant.ai/connect/docparser-to-prismix) - [ **Docparser to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docparser-to-hubspot) - [ **Docparser to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docparser-to-salesforce) - [ **Docparser to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docparser-to-slack) - [ **Docparser to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/docparser-to-google-sheets) - [ **Docparser to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docparser-to-gmail) ## More into DistrictAPI - [ **Arxiv to DistrictAPI** Open-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...](https://apiant.ai/connect/arxiv-to-districtapi) - [ **HubSpot to DistrictAPI** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-districtapi) - [ **Salesforce to DistrictAPI** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-districtapi) - [ **Slack to DistrictAPI** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-districtapi) - [ **Google Sheets to DistrictAPI** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-districtapi) - [ **Gmail to DistrictAPI** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-districtapi) Questions ## Docparser and DistrictAPI, answered ### ### What can start an automation from Docparser? Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in DistrictAPI when something happens in Docparser? Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from DistrictAPI to Docparser? DistrictAPI has no triggers in the catalog today, so automations start in Docparser. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it. ### ### Do I have to build a connector for Docparser or DistrictAPI? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Docparser and DistrictAPI without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.