This collection provides ready-to-use requests for the Fenris insurance prefill suite — covering Auto, Property, Business, and Customer 360. Use it to explore the API, validate your integration, and test requests against your Fenris-provided credentials.
\nFull API documentation: documentation.fenrisd.com
\nThe requests in this collection are pre-populated with Fenris Developer Data — artificial data provided so you can explore and test the API without incurring cost. Developer Data is not real consumer data; it is curated sample input designed to return meaningful responses from each service.
\nWhen you are ready to integrate with your own data, simply replace the request body values with your own inputs.
\nBefore making requests, configure a Postman environment with your Fenris-provided credentials:
\nIn Postman, click the + button in the left sidebar and select Environment from the dropdown menu.
\nGive your new environment a name (e.g., \"Fenris API\").
\nAdd the following variables — set client_secret to type Secret to mask the value in the Postman UI and prevent it from being shared in exports:
Click Save.
\nSelect your new environment from the environment dropdown in the top-right corner of Postman.
\nOnce your environment is active, you're ready to go. This collection includes a pre-request script that handles authentication automatically — before each request, the script checks whether a valid token exists and fetches a new one if it is missing or expired. You do not need to run the Get Bearer Token request manually.
\nPostman uses double-curly-brace syntax (e.g., Update in environment) as placeholders in requests. When a request is sent, Postman replaces these placeholders with the actual values from your environment or the collection.
Variables are resolved in this order of precedence: environment → collection. This means values you set in your environment always win over the defaults stored in the collection.
\nThis collection uses two kinds of variables:
\nVariables you provide (in your environment):
\nVariables managed automatically by the pre-request script:
\nYou never need to set or update the managed variables manually — the script handles them for you each time you send a request.
\nContact our customer success team at customersuccess@fenrisd.com.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"53869477","collectionId":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","publishedId":"2sBXitBS4b","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-04-09T20:05:15.000Z"},"item":[{"name":"Authentication","item":[{"name":"Get Bearer Token","id":"b5e0e2ba-3322-435b-a611-97728dc54b4a","request":{"auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"Update in environment"},{"key":"password","value":"Update in environment"}]},"isInherited":false},"method":"POST","header":[{"key":"Content-Type","value":"application/x-www-form-urlencoded","name":"Content-Type","type":"text"}],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"client_credentials","type":"text"}]},"url":"https://auth.fenrisd.com/realms/fenris/protocol/openid-connect/token","urlObject":{"host":["https://auth.fenrisd.com/realms/fenris/protocol/openid-connect/token"],"query":[],"variable":[]}},"response":[],"_postman_id":"b5e0e2ba-3322-435b-a611-97728dc54b4a"}],"id":"2e3cd623-780e-4ef4-aec6-efbe4b669954","description":"Fenris Digital restricts access to its APIs and manages access tokens through an OAuth2 authorization server. The Client Credentials workflow, as defined by the OAuth 2 specification, is the principal token manager. You will receive a Client ID and Client Secret used to obtain an access token from the Authorization Server.
\nFenris uses a Bearer Authentication scheme, which is one of the most commonly used methods for API Authentication. Bearer tokens can be understood as \"granting access to the bearer of this token\".
\nWhen a request is made to the Fenris Authorization Server with the Fenris-provided Client ID and Client Secret, the Authorization Server returns a bearer token. This token provides access to the restricted Fenris services when included in the Authorization header of a request. When a request to a Fenris service is sent with the bearer token, the service verifies the token is valid and controls access accordingly.
\nBearer tokens are valid for 24 hours from the time they are issued. When a token expires, the collection's pre-request script will automatically fetch a new one using your credentials.
\nYou can read more about Bearer Authentication here.
\n","_postman_id":"2e3cd623-780e-4ef4-aec6-efbe4b669954","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":""}]},"isInherited":true,"source":{"_postman_id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","name":"Fenris API Documentation","type":"collection"}}},{"name":"Property Insurance","item":[{"name":"Access Details About a Property","id":"b1fa234a-7e03-4d1c-a9fa-9acc6346e846","request":{"method":"POST","header":[{"key":"Submission-Id","value":"A pass through header field containing a client-specified identifier to tieback to client data and systems. If the client does not define, processing relies on an auto-generated field to set the value.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"addressLine1\": \"826 Kildeer Hl\",\n \"city\": \"Dayton\",\n \"state\": \"OH\",\n \"zipCode\": \"45419\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/property/v1/details/search","description":"The Fenris Digital Property - Assessment Details API quickly and accurately provides a summary of\nreported information on building characteristics, valuation, and mortgages.
\nPOST /services/property/v1/details/search
Submission-Id (header): A pass through header field containing a client-specified identifier to tieback to client data and systems. If the client does not define, processing relies on an auto-generated field to set the value.PropertyDetailsRequestPropertyDetailsResponse400401403404405415500504A pass through header field containing a client-specified identifier to tieback to client data and systems. If the client does not define, processing relies on an auto-generated field to set the value.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"addressLine1\": \"18595 Old Aldrin Highway\",\n \"city\": \"Highlands Ranch\",\n \"state\": \"CO\",\n \"zipCode\": \"80126\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/property/v1/details/search","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":""}]},"isInherited":true,"source":{"_postman_id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","name":"Fenris API Documentation","type":"collection"}},"urlObject":{"protocol":"https","path":["services","property","v1","details","search"],"host":["api.fenrisd.com"],"query":[],"variable":[]}},"response":[{"id":"0f9259f1-496f-405c-8e90-de7e173eb60f","name":"18595 Old Aldrin Highway","originalRequest":{"method":"POST","header":[{"key":"Submission-Id","value":"A pass through header field containing a client-specified identifier to tieback to client data and systems. If the client does not define, processing relies on an auto-generated field to set the value.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"addressLine1\": \"18595 Old Aldrin Highway\",\n \"city\": \"Highlands Ranch\",\n \"state\": \"CO\",\n \"zipCode\": \"80126\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/property/v1/risks/search","description":"The Fenris Digital Property - Hazards, Perils, Crime API quickly and accurately\nprovides a targeted assessment of geographic risks for property policy underwriting.\nThe categories covered by this service are:
\nIn addition to the categories above, you can obtain information on insurance premium taxes\nin applicable states, such as Kentucky.
\nPOST /services/property/v1/risks/search
Submission-Id (header): A pass through header field containing a client-specified identifier to tieback to client data and systems. If the client does not define, processing relies on an auto-generated field to set the value.PropertyRequestPropertyRiskResponse400401403404405415500504Fenris enhances property insurance with real-time data sourcing and AI-powered insights.
\nOur API provides instant access to detailed property characteristics, ownership history, and hazard risks, allowing insurers to make informed decisions quickly. By automating data retrieval and enriching applications upfront, we streamline underwriting, reduce costs, and improve the customer experience.
\nRetrieves up-to-date property details, including construction type, square footage, and ownership records.
\nAssesses natural disaster risks, such as flood or wildfire exposure, to improve underwriting accuracy.
\nUses AI-driven analytics to estimate replacement costs and market values for better policy pricing.
\n","_postman_id":"45a44ede-556a-4084-b2c0-a7aa728c44e0","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":""}]},"isInherited":true,"source":{"_postman_id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","name":"Fenris API Documentation","type":"collection"}}},{"name":"Auto Insurance","item":[{"name":"Check for violations on driver's record","id":"95319eda-6c6e-4fd1-bdd5-2edf90bb565a","request":{"method":"POST","header":[{"key":"Submission-Id","value":"A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"person\": {\n \"firstName\": \"Jenny\",\n \"lastName\": \"Everywhere\",\n \"dateOfBirth\": \"11/10/1962\"\n },\n \"address\": {\n \"addressLine1\": \"63724 Ramsey Way\",\n \"city\": \"Dallas\",\n \"state\": \"TX\",\n \"zipCode\": \"75246\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/personal/v1/driverrecord/search","description":"A request for a driver's record needs to include either the address on the license of the person of\ninterest, or the driver's license number and license state. The address component of the request is\nnot required if the driver's license is provided.
\nThis information is primarily based on a search of court records and is not a replacement for a\ncomplete Motor Vehicle Records (MVR) search. Because regulations vary across the United States, some states\nprovide more limited access to data. Driver Record Insights data is more limited in the following states; AR, CA, CO,\nDC, DE, GA, HI, KS, LA, ME, MI, MN, MO, MT, NV, NH, NY, OH, OR, TN, WV, WY.
\nPOST /services/personal/v1/driverrecord/search
Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.DriverRecordRequestDriverRecordResponse400401403404405415500504A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"person\": {\n \"firstName\": \"Jenny\",\n \"lastName\": \"Everywhere\",\n \"dateOfBirth\": \"11/10/1962\"\n },\n \"address\": {\n \"addressLine1\": \"63724 Ramsey Way\",\n \"city\": \"Dallas\",\n \"state\": \"TX\",\n \"zipCode\": \"75246\"\n },\n \"responseType\": \"M\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/personal/v1/autoprefill/search","description":"The Fenris Digital Personal Auto Insurance Prefill service provides information that can be used to quickly and\naccurately populate an auto insurance application, such as drivers and vehicle information.
\nPOST /services/personal/v1/autoprefill/search
Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.Content-Type (header): The body of the request is in JSON format, using UTF-8 character encodingAuthorization (header): The token returned from authentication. See Authentication for more detail.AutoPrefillRequestAutoPrefillResponse400401403404405415500504A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.
\n"},{"key":"Accept","value":"*/*"}],"url":"https://api.fenrisd.com/services/personal/v1/vindecoder?vin=JN8AS5MV0CW000000","description":"The VIN Decoder service provides automobile information for a requested VIN (Vehicle Identification Number).
\nGET /services/personal/v1/vindecoder
vin (query): VIN to decode.Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.Authorization (header): A Bearer token for authentication.VinDecoderResponse400401403404405415500504(Required) VIN to decode.
\n","type":"text/plain"},"key":"vin","value":"JN8AS5MV0CW000000"}],"variable":[]}},"response":[{"id":"e286cad3-833c-408d-b4ef-a1127b137158","name":"Nissan Rogue","originalRequest":{"method":"GET","header":[{"key":"Submission-Id","value":"The Fenris Digital Driver's License search service provides a driver's license number and state\nfor an input person.
\nPOST /services/driverslicense/v1/search
Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.DriversLicenseSearchRequestDriversLicenseSearchResponse400401403404405415500504There are two return options for the Auto Prefill endpoint: a base response and an enhanced response. The enhanced response includes everything in the base response, along with additional enhanced vehicle information. The response types are toggled with the responseType parameter in the request body.
\nSetting the responseType to M returns only the base data. This is the default. Setting the responseType to C returns both the base data and the enhanced vehicle information. A license is required for the enhanced vehicle information.
\nThe enhanced vehicle information is returned in the vehiclesEnhanced field in the response. This field is a list of vehicles found for the request, with each item in the list containing details for the vehicle, including the vehicle's vin number and registration.
\nExamples of each type of response can be seen in the right-hand panel, under Response samples, by toggling the options under Example. Additional details of the response fields can be seen in the Responses section below under the 200 Response Schema. The vehiclesEnhanced details can be seen by clicking the expansion carrot.
\nThe Fenris Digital Auto Prefill service provides information that can be used to quickly and accurately populate an auto insurance application, such as drivers' and vehicle information.
\n","_postman_id":"97a45a15-a8ca-4409-b23a-af59f5dd6e36","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":""}]},"isInherited":true,"source":{"_postman_id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","name":"Fenris API Documentation","type":"collection"}}},{"name":"Commercial Insurance","item":[{"name":"Prefill Information about a Business","id":"4147733c-ca71-4167-8d91-2adba4a5eb27","request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json","type":"text"},{"key":"fenris-disable-cache","value":"true","type":"text"}],"body":{"mode":"raw","raw":"{\n \"names\": [\n \"Cherry on Top Cupcake\",\n \"Cherry on Top Bakery\",\n \"Cherry Cupcake Midtown\",\n \"Cherry Cupcakes\"\n ],\n \"address\": {\n \"addressLine1\": \"32301 Juergensen ST NW\",\n \"city\": \"Washington\",\n \"state\": \"DC\",\n \"zipCode\": \"20007\"\n }\n}"},"url":"https://api.fenrisd.com/services/smb/v1/search","description":"Using only a business name and address, the Fenris Digital Business Insurance Prefill API locates and\nreturns extensive business details. This API leverages the Fenris best-in-class match rates to return a\nrobust set of data fields in a matter of seconds.
\nOur client's tell us that if they are the first to quote a business, they will have greater than 60% chance\nof closing that lead. Business Insurance Prefill provides crucial time-saving results for agents and brokers\nwho are trying to gather applicant information and for underwriters who are key in the quote/close policy\nphase.
\nThe Commercial Insurance Prefill service works by matching a request including one or more business names,\nand one or more business addresses to several data repositories.
\nWhen a request is received, the provided business name(s) are cleansed by removing common business terms\nthat are often swapped or abbreviated (e.g., Ltd, LLC, Inc.), and the address(es) are standardized to USPS\nform using the Fenris address standardization service.
\nThe cleansed names and addresses are then used to search the Fenris Commercial Reference Data.\nThis search attempts to find the business at the location(s) entered using fuzzy matching on the name(s).
\nIf no match is found for the name and address, the search is expanded by looking across the state for\nbusinesses that match the input name (Note: many businesses have multiple names, and this is reflected in\nthe reference data that is searched).
\nIf no match is found in the commercial reference data with either approach, then the same names and\naddresses are used to search the Fenris consumer reference data.
\nWhile the Fenris reference data is being searched, the service also queries the Secretary of State data for\nthe state in the address field of the request. This search is based only on the business name and\nthe input state.
\nOnce the searches are complete, the service aggregates all of the matched data from the sources and returns\nit. There are three fields in the return that provide information about the results of the searches. They\nare status, matchDescription, and\naddressDescription`.
POST /services/smb/v1/search
fenris-match-logic (header): Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.BusinessRequestBusinessResponse400401403404405415500504A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.
\n"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"*/*"}],"body":{"mode":"raw","raw":"{\n \"names\": [\n \"Cherry on Top Cupcake\",\n \"Cherry on Top Bakery\",\n \"Cherry Cupcake Midtown\",\n \"Cherry Cupcakes\"\n ],\n \"address\": {\n \"addressLine1\": \"32301 Juergensen ST NW\",\n \"city\": \"Washington\",\n \"state\": \"DC\",\n \"zipCode\": \"20007\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/smb/v1/financial/search","description":"The Fenris Digital Business Financial Information API locates and returns details on the financial health\nof the searched business, including scores estimating the businesses' risk of becoming severely delinquent\nor filing for bankruptcy.
\nThis API leverages the Fenris best-in-class match rates to return a robust set of data fields in a matter\nof seconds.
\nPOST /services/smb/v1/financial/search
Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.BusinessRequestCreditResponse400401403404405415500504Using only a business name and address, the Fenris Digital Business Insurance Prefill API locates and returns extensive business details. This API leverages the Fenris best-in-class match rates to return a robust set of data fields in a matter of seconds.
\nThe Commercial Insurance Prefill service works by matching a request, including one or more business names and one or more business addresses, to several data repositories.
\nWhen a request is received, the provided business name(s) are cleansed by removing common business terms that are often swapped or abbreviated (e.g., Ltd, LLC, Inc.), and the address(es) are standardized to USPS form using the Fenris address standardization service.
\nThe cleansed names and addresses are then used to search the Fenris Commercial Reference Data. This search attempts to find the business at the location(s) entered using fuzzy matching on the name(s).
\nIf no match is found for the name and address, the search is expanded by looking across the state for businesses that match the input name (Note: many businesses have multiple names, and this is reflected in the reference data that is searched).
\nIf no match is found in the commercial reference data with either approach, then the same names and addresses are used to search the Fenris consumer reference data.
\nWhile the Fenris reference data is being searched, the service also queries the Secretary of State data for the state in the address field of the request. This search is based only on the business name and the input state.
\nOnce the searches are complete, the service aggregates all of the matched data from the sources and returns it. There are three fields in the return that provide information about the results of the searches. They are status, matchDescription, and addressDescription.
The Customer 360 API quickly and accurately populates household information into\napplication forms, making the insurance application process seamless.
\nThe Customer 360 service returns information that can also be used to advise an agent or system about the\nfinancial and family status of the applicant. This includes information such as the presence of children\nand mortgage data. This information can be used to make sure that the applicant has the coverage that\nfits their needs.
\nPOST /services/lifeprefill/v1/search
Submission-Id (header): A pass through field from the request header containing a client-specified identifier to tieback to client data and systems. If the client does not define this value, an auto-generated field is used.LifePrefillRequestLifePrefillResponse400401403404405415500504When dealing with internet lead generation, you can expect invalid contacts containing errors due to\ntypos on forms or intentionally false information. What if you could practically ensure valid leads with\naccurate contact information? The Fenris Digital (\"Fenris\") Profile+ service validates the contact\ninformation on leads to ensure that you are contacting real people instead of wasting time trying to\ncontact people who don't exist, at fake addresses, with autogenerated, made-up email addresses. The\nfirst chance a client has to evaluate whether they can contact a lead occurs when they first receive the\nPOST data. By using FenrisProfile+ service, clients get instant feedback on the quality of the contact\ninformation so that they can route the request to the appropriate channel or return the lead to the seller.
\nThe FenrisProfile+ Service works by comparing the input contact information such as person's\nname, postal address, e-mail address, phone number to Fenris' reference database of more than 250\nmillion individuals and 130 million households to determine whether the input person exists in its\nreference data to determine the viability of making contact with the lead. These results are also passed\nto Fenris' proprietary Profile+ scoring engine to compute a score that enables quick assessment on\nthe viability of outreach to each lead based on all of the input contact data submitted.
\nWe match each lead to our proprietary, multi-sourced database covering more than 97% of the US\npopulation, evaluating validity for each element so you can sift out fraudulent entries. You can decide at\nthat point to purchase or return the lead, or you can run validated leads through the Fenris data\nenrichment and lead scoring APIs for an even more granular assessment of lead quality and likelihood to\nbuy.
\nThe FenrisProfile+ endpoint receives a lead's contact data and returns information on the validity of the\nelements submitted. Note that all items in the request are optional. Information will be provided only for\nthe submitted elements.
\nTest the FenrisProfile+ service with our Personal Developer Data.\nThe developer data is synthetically generated and contains no PII. Requests made with developer\ndata are not charged to your account.
\nPOST /services/truprofile/v1/profile
fenris-model-type (header): Allows users with a deployed tailored model to use the generic FenrisProfile+ model by specify generic as\nthe value.ProfileRequestProfileResponse400401403404405415500504The Customer 360 API quickly and accurately populates household information into application forms, making the insurance application process seamless.
\nThe Customer 360 service returns information that can also be used to advise an agent or system about the financial and family status of the applicant. This includes information such as the presence of children and mortgage data. This information can be used to make sure that the applicant has the coverage that fits their needs.
\nWhen dealing with internet lead generation, you can expect invalid contacts containing errors due to typos on forms or intentionally false information. What if you could practically ensure valid leads with accurate contact information? The Fenris Digital (\"Fenris\") Profile+ service validates the contact information on leads to ensure that you are contacting real people instead of wasting time trying to contact people who don't exist, at fake addresses, with autogenerated, made-up email addresses. The first chance a client has to evaluate whether they can contact a lead occurs when they first receive the POST data. By using Fenris Profile+ service, clients get instant feedback on the quality of the contact information so that they can route the request to the appropriate channel or return the lead to the seller.
\nThe Fenris Profile+ Service works by comparing the input contact information such as person's name, postal address, e-mail address, phone number to Fenris' reference database of more than 250 million individuals and 130 million households to determine whether the input person exists in its reference data to determine the viability of making contact with the lead. These results are also passed to Fenris' proprietary Profile+ scoring engine to compute a score that enables quick assessment on the viability of outreach to each lead based on all of the input contact data submitted.
\nWe match each lead to our proprietary, multi-sourced database covering more than 97% of the US population, evaluating validity for each element so you can sift out fraudulent entries. You can decide at that point to purchase or return the lead, or you can run validated leads through the Fenris data enrichment and lead scoring APIs for an even more granular assessment of lead quality and likelihood to buy.
\n","_postman_id":"619020ae-f61f-4678-af18-e4d787aa7584","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":""}]},"isInherited":true,"source":{"_postman_id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","id":"3cdab93b-e683-4771-9ecc-8c9d150ac80b","name":"Fenris API Documentation","type":"collection"}}},{"name":"Echo","id":"5d163710-151b-4817-9373-732014ffffbd","request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"message\": \"Hello world!\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.fenrisd.com/services/echo/v1/echo","description":"Echoes the message sent to it. A useful service for testing authentication and connectivity.
\nPOST /services/echo/v1/echo
EchoRequestEchoResponse400401403404405415500504