---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/security-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Create an API connector using Now Assist for Vulnerability Response

# Create an API connector with Now Assist for Vulnerability Response {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Use the SPC Setup Connector skill to help you automatically complete configuration steps 3-5 in the Connector builder in the Security Posture Control Workspace.

## Antes de Iniciar

The SPC Setup Connector skill is included with Now Assist for Vulnerability Response and the skill is activated by default. For more information about configuring this skill, see [Configure a skill for Now Assist for Vulnerability Response](https://servicenow-prod.fluidtopics.net/gzJYxGzACodDms0nWirj4A "You have the option to review the details, edit the configuration of a skill, and reactivate it in the Guided Setup.").  
Importante:  
This Now Assist skill is turned on by default. The skill will be automatically available to appropriate role users for the application. For more information, see [Now Assist skills, agents, and agentic workflows on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).

You must complete steps one and two in the workspace before you can invoke the SCP Setup Connector Now Assist skill. See [Enter metadata](https://servicenow-prod.fluidtopics.net/gPBCr~ewDa9DFx79mS8S~A "Fill in the metadata for your service graph connector.") and [Create connector alias and connection credentials](https://servicenow-prod.fluidtopics.net/iK7TTpmQiy6Pli~3uWHyaQ "Enter the connection URL and credential alias details for your API connector.") for more information.

Role required: admin

## Procedimento

1. Navigate to AllSecurity Posture ControlConnector builder and complete steps 1 and 2, if not already completed.
2. In step 3, select Use Now Assist.
3. Fill in the fields.  
   Nota:  
   An error is displayed if the API document URL is not supported, or it is not related to asset listing data.
   {#select-api-template__entry__2}

   | Field | Description |
   |-|-|
   | API Document Link | Enter the URL for the vendor that has API information you want to use, for example, https://developer.yourvendor.com/documentation/api/assets. |
   | API Endpoint (Optional) | You might prefer to use this field if the API page has too many details, or if it's a PDF, or if it's in JASON and not HTML format. You can add an endpoint to a base URL. For example, you have https://developer.yourvendor.com. Locate the endpoint you want in the API documentation (documentation/api/assets) and enter it in this field. |
   [ ]

4. Select Set it up for me.  
   The Now Assist skill automatically selects a template, provides input parameters, tests the API connection, and maps parameters.

   The process takes a few moments and progress is displayed in the modal.

   Now Assist generates a response sample and schema based on the API documentation you uploaded in the previous step. You must check the sample response and schema for accuracy and the mapping for accuracy before
   you [validate your connector](https://servicenow-prod.fluidtopics.net/PoOd952v7ftGIxHwNtLqog "Test the connection for your API connector. You must pass both checks before you can publish your connector. You must review your input and mapping to be sure that it is accurate before publishing your connector.") and publish it.  
   Nota:  
   A warning message is displayed that prompts you to review and verify that all the information generated by the Now Assist skill is correct.

   An error message is displayed if the Now Assist skill cannot provide input, for example, if it cannot select a template based on the information you provided. If you see an error message, you cannot select Apply configuration and proceed to the next step.
5. Select Apply configuration.  
   The Select template step in the Connector builder is displayed and a template had been automatically selected.
6. Select Save and continue.  
   The Provide inputs step is displayed. The following information is automatically populated in the form for you based on the vendor documentation that you provided.  
   Nota:  
   You do not need to select Get sample response.
   * API sample response
   * API endpoint path
   * Query parameters
   * Header parameters
   * Pagination parameters
   {#select-api-template__ul_x54_fc2_fhc}
7. Review the information and edit the fields as needed.
8. Select Save and continue after you have reviewed the values.  
   If you do not see an API sample, or an error is displayed, follow the prompts in the message to enter any missing values.

   The Map response step is displayed after a successful import. The input parameters have been mapped automatically to Security Posture Control (SPC) attributes and policies from the sample data generated by your connector.

   Verify the values by reviewing the API response sample for SPC attributes and the API response schema sample for API attributes in the Reference window.

   This sample data is aggregated, and the mapping is editable. Additionally, you can and create custom attributes for your SPC policies as needed.

   For more information about mapping that includes combining values to populate a single field, see [Map response](https://servicenow-prod.fluidtopics.net/~Axp8jcO1KnNgyfX56u4yQ "Map API response properties to SPC attributes.￼ After you have mapped the attributes, you publish your connector so it imports data.") in the Security Posture Control product documentation.
9. See [validate your connector](https://servicenow-prod.fluidtopics.net/PoOd952v7ftGIxHwNtLqog "Test the connection for your API connector. You must pass both checks before you can publish your connector. You must review your input and mapping to be sure that it is accurate before publishing your connector.") in the Security Posture Control product documentation for more information about the validation step, publishing your connector, and completing the process.

