--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # REST API connector # REST API connector for Zero Copy Connector for ERP {#ariaid-title1} Release version: Australia Updated October 20, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of REST API connector for Zero Copy Connector for ERP The REST API connector for Zero Copy Connector for ERP enables ServiceNow customers to integrate with any RESTful API using standardized API specifications. It provides a reusable, low-code integration layer to access business data from ERP systems, simplifying what traditionally requires manual integration efforts. Show full answer Show less ## Key Features * **Connection Configuration:** REST connections use an HTTP connection template, allowing seamless setup of REST service connections. * **Authentication Support:** Supports multiple authentication methods including Basic Auth, JWT bearer tokens, API keys (in headers or query parameters), and OAuth 2.0 with automatic token refresh. Credentials are securely stored in ServiceNow Vault. * **API Definition Import:** Import REST API definitions via Swagger/OpenAPI URLs or upload JSON/YAML specification files. The system automatically extracts and allows customization of the service name and makes all matching endpoints available for selection. * **Data Mapping:** Use Model Manager to define entities and map API response fields to your data model, enabling structured data integration. * **MID Server Support:** For REST APIs hosted on-premises or behind firewalls, API calls can be routed through a MID Server to maintain secure connectivity. Cloud-hosted APIs connect directly without requiring a MID Server. * **Supporting Tables:** The connector includes dedicated tables to support Zero Copy Connector for ERP operations and data management. ## Practical Benefits ServiceNow customers can leverage this connector to efficiently integrate ERP system data into their workflows without extensive coding. It streamlines authentication handling, API specification management, and data mapping, ensuring secure and reliable connectivity whether APIs are cloud-based or on-premises. This accelerates ERP data access and automation within ServiceNow environments. Use the REST API connector to connect to any RESTful API with standardized API specification formats. ## Overview of REST API connector {#erp-rest-api-connector__section_d3v_ywc_j3c} You can use REST APIs to access business data from ERP (Enterprise Resource Planning) systems. Integrating these APIs requires manual processes. The REST API connector solves this by providing a reusable, low-code integration layer. For API details, see . ## REST service connection configuration {#erp-rest-api-connector__section_i5n_rxc_j3c} REST connections use the HTTP connection template. For more information, see [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=australia&pubname=australia-platform-security&ft:locale=en-US). ## Authentication options {#erp-rest-api-connector__section_gxx_vyc_j3c} The connector supports the following authentication options: * Basic Auth: A username and password (Base64-encoded). For more information, see [Basic authentication credential](https://www.servicenow.com/docs/access?context=r_BasicAuthCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US). * JWT (JSON Web Token): A bearer token authentication. For more information, see [JWT Bearer](https://www.servicenow.com/docs/access?context=jwt-bearer&version=australia&pubname=australia-platform-security&ft:locale=en-US). * API Key: A key passed as a header or query parameter. For more information, see [API key credentials](https://www.servicenow.com/docs/access?context=API-key-credential-form&version=australia&pubname=australia-platform-security&ft:locale=en-US). * OAuth 2.0: A token authentication with automatic token refresh. For more information, see [Manage OAuth tokens](https://www.servicenow.com/docs/access?context=t_ManageTokens&version=australia&pubname=australia-platform-security&ft:locale=en-US). {#erp-rest-api-connector__ul_cmc_pzc_j3c} ServiceNow Vault stores credentials securely. For more information, see [Exploring ServiceNow Vault](https://www.servicenow.com/docs/access?context=exploring-servicenow-vault&version=australia&pubname=australia-platform-security&ft:locale=en-US). The system validates that the configured credential type matches one of the authentication schemes defined in the API specification before allowing execution. ## Importing a REST API definition into the Zero Copy Connector for ERP Model Manager {#erp-rest-api-connector__section_l5m_jyc_j3c} Import a REST API definition using one of the following methods: * Use the Swagger/OpenAPI URL and provide a public URL that points to a specification file. The system extracts the service name from the URL automatically. You can edit the service name before adding the service. After the service is added, all endpoints matching the current operation type become available for selection. * Upload a Swagger/OpenAPI JSON or Swagger/OpenAPI YAML file. {#erp-rest-api-connector__ul_ppd_1yc_j3c} ## Mapping data to your data model {#erp-rest-api-connector__section_vql_qzc_j3c} After you import a REST service, use the Model Manager to define entities and map API response fields to the data model. For more information, see [Add a REST entity to a model operation](https://www.servicenow.com/docs/hBTaDfb0bjtK6npAnkbawg "Specify the REST entity that a Zero Copy Connector for ERP (Enterprise Resource Planning) model uses for a read, update, or create operation."). ## MID Server support {#erp-rest-api-connector__section_zyn_qc2_j3c} If your REST API runs on-premises or behind a firewall, you can route API calls through a MID Server. The connection record includes a midServerName property that routes traffic through the designated MID Server. Cloud-hosted APIs can connect directly without a MID Server. For more information, see [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). ## REST API connector tables {#erp-rest-api-connector__section_ojb_xc2_j3c} For information about the REST API connector tables that support Zero Copy Connector for ERP, see [REST API connector tables for Zero Copy Connector for ERP](https://www.servicenow.com/docs/WkjdIdyMYLImZEf4QPqzwA "The REST API connector in Zero Copy Connector for ERP (Enterprise Resource Planning) uses these tables to store service definitions, endpoint definitions, and model metadata.").