{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":15516,"path":"financial-services-operations/configure-rest-end-point.md","title":null,"bundle":null,"doc_type":null,"release":null,"body":"---\ntitle: Configure the REST End Point\ndescription: The REST Endpoint record in ServiceNow stores the base URL, API version header, and connection properties for the Verifi API. Create two endpoint records: one for UAT testing and one for Production.\nlocale: en-US\ncanonical_url: https://www.servicenow.com/docs/r/australia/financial-services-operations/configure-rest-end-point.html\nrelease: australia\ntopic_type: task\nlast_updated: \"2026-04-02\"\nreading_time_minutes: 2\nbreadcrumb: [Configure, Verifi, Integrate, Financial Services Operations \\(FSO\\)]\n---\n\n# Configure the REST End Point\n\nThe REST Endpoint record in ServiceNow® stores the base URL, API version header, and connection properties for the Verifi API. Create two endpoint records: one for UAT testing and one for Production.\n\n## Before you begin\n\nRole required: admin\n\n## Procedure\n\n1.  Create the UAT Endpoint.\n\n    1.  Navigate to System Web Services > Outbound > REST messages.\n\n    2.  Select **New**.\n\n    3.  Populate the following fields as shown:\n\n        |Field|Value|\n        |-----|-----|\n        |Name|Verifi CDRN API — UAT.|\n        |Description|Verifi CDRN — UAT / Integration Testing.|\n        |Endpoint|https://verifiapitest.visa.com|\n        |Authentication type|No Authentication \\(JWT is included via the scripted header.|\n\n    4.  Under HTTP Request, add the following default headers \\(these apply to ALL methods\\):\n\n        |Header Name|Value|Notes|\n        |-----------|-----|-----|\n        |Accept|application/json|Required on all calls \\(GET, POST, PATCH\\).|\n        |x-verifi-api-version|4.0|Must match the API version supported by your integration.|\n        |x-verifi-issuer|$\\{verifi\\_issuer\\_id\\}|Populated at runtime from the Credential Store — see Section 5.|\n\n        **Note:**\n\n        Do not add Content-Type: application/json as a default header on the REST Message record. The Verifi guide specifies Content-Type is required on POST and PATCH requests only and not on GET requests. Set Content-Type at the individual HTTP Method level for each POST and PATCH method \\(see Section 3.4\\). Sending Content-Type on GET calls may cause the request to get rejected.\n\n    5.  Select **Submit** to save the record.\n\n    6.  Add HTTP Methods \\(POST, GET, PATCH\\)\n\n    **Note:**\n\n    The Verifi Issuer API supports HTTP/1.0 calls over HTTPS only. ServiceNow outbound REST defaults to HTTP/1.1. Confirm with your ServiceNow platform administrator whether HTTP version can be restricted at the REST Message or MID Server level, or verify with Verifi that HTTP/1.1 is accepted in practice before going live.\n\n    |UAT / Test|https://verifiapitest.visa.com|4.0|\n    |----------|------------------------------|---|\n    |Environment|Base URL|API Version Header|\n    |Production|https://verifiapi.visa.com|4.0|\n\n2.  Create the production endpoint.\n\n    |**Field**|**UAT Value**|**Production Value**|\n    |---------|-------------|--------------------|\n    |Name|Verifi CDRN API — UAT|Verifi CDRN API — Production|\n    |Endpoint|https://verifiapitest.visa.com|https://verifiapi.visa.com|\n    |Description|UAT / Integration Testing|Production environment — live transactions|\n\n    **Note:** Do not point a UAT Issuer ID or Shared Secret at the Production endpoint. Doing so will result in rejected API calls and may generate alerts in the Verifi production environment.\n\n3.  Enter HTTP Methods per Endpoint.\n\n    Each REST Message record requires individual HTTP Method entries. Create the following methods under both the UAT and Production endpoint records.\n\n    |HTTP Method|ServiceNow Method Name|Relative URL|Used For|\n    |-----------|----------------------|------------|--------|\n    |POST|Create Case|/issuers/cases|Submit a new CDRN dispute or inquire.|\n    |GET|Get Case|/issuers/cases/$\\{case\\_id\\}|Poll for status on a single case.|\n    |GET|Get Multiple Cases|/issuers/cases?caseId=$\\{case\\_ids\\}|Poll status for multiple cases in one call.|\n    |PATCH|Update Case|/issuers/cases/$\\{case\\_id\\}|Close or revoke a case.|\n    |GET|Get Descriptor List|/issuers/descriptors|Retrieve eligible merchant descriptors \\(optional\\).|\n\n    **Note:** The Authorization header containing the encoded JWT is set dynamically at runtime per call, not at the HTTP Method level.\n\n\n**Parent Topic:**[Configuring Financial Services Operations Integration with Verifi](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/configure-financial-services-integration-with-verifi-cdrn.md)\n\n"}}